Earlier quoted context omitted.
https://github.com/openssh/openssh-portable/blob/e6c85f8889c... Here you go
Actually, I quickly generated a list of undocumented config options: http://sprunge.us/QDSE Edit: Fixed version http://sprunge.us/LVYB
OpenSSH: client bug CVE-2016-0777
71–80 of 226 posts
Re: OpenSSH: client bug CVE-2016-0777
#72Earlier quoted context omitted.
It's from the linked page.
Indeed. The page gives bad advise. If your config has `Host` blocks, like often in people's personal configs, or if you have a `Match` block, the new directive only applies to the last of those blocks in the config file.
Host *
UseRoaming noRe: OpenSSH: client bug CVE-2016-0777
#73Does it strike anyone else as bizarre / poor form for an experimental feature to be enabled by default in OpenSSH, which is normally very conservative with option defaults?
It just sounds like a big code-base fuckup. They more or less admit it: "Server side was disabled/gutted for years already, but this aspect was surprisingly forgotten." Sounds like this was put in at one time, forgotten about, and the code lingered for a long time until someone pointed it out. SSH as a protocol is pretty crazy. Everyone loves it, but its a lot of things in one, which ironically goes against the unix…
Re: OpenSSH: client bug CVE-2016-0777
#74Does it strike anyone else as bizarre / poor form for an experimental feature to be enabled by default in OpenSSH, which is normally very conservative with option defaults?
It just sounds like a big code-base fuckup. They more or less admit it: "Server side was disabled/gutted for years already, but this aspect was surprisingly forgotten." Sounds like this was put in at one time, forgotten about, and the code lingered for a long time until someone pointed it out. SSH as a protocol is pretty crazy. Everyone loves it, but its a lot of things in one, which ironically goes against the unix…
http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man2/...
Re: OpenSSH: client bug CVE-2016-0777
#75Earlier quoted context omitted.
Actually, I quickly generated a list of undocumented config options: http://sprunge.us/QDSE Edit: Fixed version http://sprunge.us/LVYB
I believe "kerberosauthentication" and "rhostsauthentication" are documented as well. I'd check the "official" OpenBSD man page instead of whatever you have on your system. Regardless, thanks.
Re: OpenSSH: client bug CVE-2016-0777
#76Earlier quoted context omitted.
Is there any way to update openssh on my side, without waiting to apple ? Is this enough ? https://mochtu.de/2015/01/07/updating-openssh-on-mac-os-x-10...
Even easier, just place this text: UseRoaming no on its own line in your ~/.ssh/config file. If you don't have such a file, create it and put this line into it. Doing that will only protect you in that OS X user account, but I bet you only ever use one account on your Mac to SSH anyway.
Re: OpenSSH: client bug CVE-2016-0777
#77Earlier quoted context omitted.
Actually, I quickly generated a list of undocumented config options: http://sprunge.us/QDSE Edit: Fixed version http://sprunge.us/LVYB
I believe "kerberosauthentication" and "rhostsauthentication" are documented as well. I'd check the "official" OpenBSD man page instead of whatever you have on your system. Regardless, thanks.
Re: OpenSSH: client bug CVE-2016-0777
#78Re: OpenSSH: client bug CVE-2016-0777
#79If it's not obvious, don't just add that config option, you have to also restart it. Actually wait, is this only affecting the ssh client and not the server/daemon ?