<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear Rainer,<div class=""><br class=""></div><div class="">Thanks for the response.</div><div class=""><br class=""></div><div class="">I can attest that openssh+gsskex does not support keychain, because my port installation is openssh @7.6p1_2+gsskex+kerberos5+xauth.</div><div class=""><br class=""></div><div class="">This puts me in a dilemma. I need for one particular remote system the gsskex support, which was removed by Apple quite some time ago. That was why I started using macports’ version in the first place.</div><div class=""><br class=""></div><div class="">I guess the only thing I can do is to make a special alias for that remote system using the macports’ openssh, and use Apple’s version for all others. This is annoying that Apple is customizing its own ssh…</div><div class=""><br class=""></div><div class="">Sincerely,</div><div class=""><div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Chao-Chin</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></div></div><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Feb 5, 2018, at 6:55 AM, Rainer Müller <<a href="mailto:raimue@macports.org" class="">raimue@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 2018-01-31 21:28, Chao-Chin Yang wrote:<br class=""><blockquote type="cite" class="">I can continue to log into the remote system without entering again the<br class="">passphrase. However, once I completely log out of my Mac and re-log<br class="">into my Mac, the terminal does not remember my passphrase anymore.<br class=""></blockquote><br class="">As of macOS 10.12 Sierra, this is the intended behavior:<br class=""><br class=""><a href="https://developer.apple.com/library/content/technotes/tn2449/_index.html#//apple_ref/doc/uid/DTS40017589" class="">https://developer.apple.com/library/content/technotes/tn2449/_index.html#//apple_ref/doc/uid/DTS40017589</a><br class=""><br class=""><blockquote type="cite" class="">After googling around, it seems that the Mac native SSH has added a new<br class="">SSH keyword “UseKeychain”, while the MacPorts version does not have this<br class="">keyword and is having problem talking to Keychain. I cannot find any<br class="">solution to this.<br class=""><br class="">Does anyone know any solution or is working on one?<br class=""></blockquote><br class="">Unfortunately, the keychain support is a custom patch by Apple that is<br class="">not in the upstream sources. The patch will only be applied when<br class="">installing it with the +gsskex variant, however, I have not tested it<br class="">myself.<br class=""><br class="">Personally, I usually use /usr/bin/ssh because of the keychain<br class="">integration, but I have the following lines in my ~/.ssh/config that<br class="">stop /opt/local/bin/ssh from choking on the unknown options:<br class=""><br class=""> IgnoreUnknown AddKeysToAgent,UseKeychain<br class=""> AddKeysToAgent yes<br class=""> UseKeychain yes<br class=""><br class="">Hope that helps,<br class="">Rainer<br class=""></div></div></blockquote></div><br class=""></div></body></html>