News for hackers. Stuff that matters.
Re:OpenSSH sshd – memory leak by jacquesm on Monday May 05, 2014 @06:15PM (#7701641)
Well, technically after a fork you have access to all the childs memory pages, they're identical to your own (that is, until any writes happen, usually that's when copies are made and each process ends up with a different version of that page). But then the 'exec' bit happens and it's a completely new process. Any access to memory of the child process thereafter would be through some deliberate mechanism unless there is a significant issue with the underlying operating systems ability to keep processes where they belong (separated).

The whole idea is that processes have separate memory spaces, debuggers, shared memory applications and IPC implementation work hard to do this on purpose.

If sshd really had unfettered access to its child processes then so would every other process that spawns some new process, init comes to mind as a nice candidate, cron as another (though neither exposes network sockets).

Of course, a process running as 'root' has technically access to all the other processes memory through (on Linux) /dev/mem (phys) and /dev/kmem (virt) but you have to open it first and as far as I'm aware sshd does not do this.

Re:OpenSSH sshd – memory leak by nitrogen on Monday May 05, 2014 @06:45PM (#7701774)
...(though neither exposes network sockets).

I'm not sure, but that may no longer be true with systemd.