Agreed... this looks more like pilot error than anything else.
The update caught be by surprise. I should have known better, though...
if my config file had not been modified by me or my Virtuozzo provider,
then I would not have been asked whether or not I wanted the new change.
In either case,
** Changed in: openssh (Ubuntu)
Status: New = Opinion
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/707098
Opinion isn't the right status here.
Alan, firstly (and tangentially, I suppose), the openssh update was a
normal update, not a security update. That aside, we didn't change the
oom line in that update, only the expect and exec lines. Here's
the full diff:
Looking a little deeper, it looks like OpenSSH has had this oom never
line ever since Ubuntu 10.04 came out, and that Virtuozzo containers
have had to modify this file all along. I never saw it before because
my Virtuozzo provider had a pristine 10.04 image that they deployed -- I
assume, with
