© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This is a serious security bug in my opinion. Many network security processes are started on boot by init via upstart. If you have a server running fail2ban, for instance, and ssh/etc is not set to be dependent on fail2ban with the understanding that fail2ban will be initialized on boot... this leads to a potentially serious situation.
Keep in mind that on a headless server, an update/reboot to this buggy version of upstart may also prevent some main access protocol to the server from being initialized. This is a bad problem.
On 9.10 64-bit, I reverted to 0.6.3.10 and rebooted, to find my system once again initializing everything that it should.