News for hackers. Stuff that matters.
Re:CVE-2014-6271: Remote code execution through bash by _wmd on Wednesday September 24, 2014 @11:38AM (#8362060)
As an example of who might be impacted, since openssh preserves the original command line passed to the ssh server when authenticating a public key that has a fixed command associated in authorized_keys, GitHub and BitBucket security teams are probably both having a really exciting day.
Re:CVE-2014-6271: Remote code execution through bash by scintill76 on Wednesday September 24, 2014 @03:24PM (#8363559)
This vulnerability is the kind of reason I would have a stripped-down OpenSSH for public users, if I were them. Hard-code to do what they need, don't use configuration files, remove any features not needed. For example, to print the "You've successfully authenticated, but GitHub does not provide shell access." a user gets trying to ssh to github.com, don't invoke anything, print it directly from the SSH server.
Re:CVE-2014-6271: Remote code execution through bash by graylights on Wednesday September 24, 2014 @04:55PM (#8364080)
Much easier to implement a custom captive shell (default login shell for user) then to mess with the crypto system.
Re:CVE-2014-6271: Remote code execution through bash by scintill76 on Wednesday September 24, 2014 @05:56PM (#8364389)
Maybe. Actually, it looks like Github is using libssh, which is along the lines of what I was thinking, without having to mess with crypto too much, as you say.
Re:CVE-2014-6271: Remote code execution through bash by thejosh on Wednesday September 24, 2014 @08:05PM (#8364843)
This is what Atlassian Stash does.