News for hackers. Stuff that matters.
Re:OpenSSH security advisory by pattt on Friday November 08, 2013 @07:40AM (#6695739)
"This vulnerability is mitigated by the difficulty of pre-loading the heap with a useful callback address and by any platform address-space layout randomisation applied to sshd and the shared libraries it depends upon."

Right. But in order for RoP explotation (say chain some libc function calls) to work you'd still have to manipulate the stack arguments in some fancy way, also it's not really sure how trivial is "pre-loading the heap" since it's a post-authentication stage bug as the advisory mentions. Of course these are just speculation, digging into the source code might change perspective :)

Re:OpenSSH security advisory by antocv on Friday November 08, 2013 @11:17AM (#6697014)
Yes it is quite comforting this is post-authentication, so in most cases no big deal. Just tough luck for shared accounts.

I guess most people dont run sshd as root and capabilities either so that minimizes damage too. Another reason to not run ssh on port 22, no root, no special caps needed.

Re:OpenSSH security advisory by Nick_C on Friday November 08, 2013 @10:18PM (#6700533)
All my servers run sshd as root, including the FreeBSD ones. Is that ok? Or do you mean that sshd drops privileges for the child after forking?