I think the debian patch had been applied in releases after Hardy. But the daemon only resets the oom_adj value that it was originally called with. So in Jaunty a DHCP restart script which had the oob_adj value of -17 itself caused the same effect. See bug report #390556.
I have not checked lucid yet. But the issue itself caused me a lot of headaches and it would have been nice if it would have been fixed back in 2008 in a Ubuntu version which is labeled "LTS". -- hardy: openssh-server oom_adj can lead to denial of service https://bugs.launchpad.net/bugs/293000 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
