3 ms·

If you just want to upgrade bash, and prevent services like nginx, fpm, and apache from being restarted in production, you can run `sudo apt-get update && sudo

by vhost- 12y ago

If you just want to upgrade bash, and prevent services like nginx, fpm, and apache from being restarted in production, you can run `sudo apt-get update && sudo apt-get install --only-upgrade bash` Related to that, does anyone else know if upgrading bash will require a restart of other services kind of like upgrading openssl requires restarting things?

auxiliation 12y ago
> Related to that, does anyone else know if upgrading bash will require a restart of other services kind of like upgrading openssl requires restarting things? I don't think it will, for a couple of reasons. OpenSSL is integrated into other services as a library, while bash would be called as an external application. I also noticed that once I upgraded bash, the proof of concept stopped working in a terminal I opened prior to the upgrade.
- fragmede 12y ago
  > I also noticed that once I upgraded bash, the proof of concept stopped working in a terminal I opened prior to the upgrade. [citation needed] because that doesn't sound possible.
  - lutusp 12y ago
    Not if the issued commands spawned a new copy of Bash.
  - deleted 12y ago
    [deleted]
euid 12y ago
Upgrades should not require any restarts, and no restarts are required for you to stop being vulnerable - as this only affects newly created bash sessions, not already running ones.
- stefantalpalaru 12y ago
  Debian's package manager has the nasty habit of stopping affected daemons before all the upgrades and starting them afterwards, leaving you with serious downtime.
jMyles 12y ago
It runs out that these suggestions were premature, the patch released earlier today DOES NOT fix the problem. https://bugzilla.redhat.com/show_bug.cgi?id=1141597#c24 https://bugzilla.redhat.com/show_bug.cgi?id=1141597#c24 I just tested this on Ubuntu 14.04 - it's vulnerable.

3 ms·

If you just want to upgrade bash, and prevent services like nginx, fpm, and apache from being restarted in production, you can run `sudo apt-get update && sudo

by vhost- 12y ago

auxiliation 12y ago
> Related to that, does anyone else know if upgrading bash will require a restart of other services kind of like upgrading openssl requires restarting things? I don't think it will, for a couple of reasons. OpenSSL is integrated into other services as a library, while bash would be called as an external application. I also noticed that once I upgraded bash, the proof of concept stopped working in a terminal I opened prior to the upgrade.
- fragmede 12y ago
  > I also noticed that once I upgraded bash, the proof of concept stopped working in a terminal I opened prior to the upgrade. [citation needed] because that doesn't sound possible.
  - lutusp 12y ago
    Not if the issued commands spawned a new copy of Bash.
  - deleted 12y ago
    [deleted]
euid 12y ago
Upgrades should not require any restarts, and no restarts are required for you to stop being vulnerable - as this only affects newly created bash sessions, not already running ones.
- stefantalpalaru 12y ago
  Debian's package manager has the nasty habit of stopping affected daemons before all the upgrades and starting them afterwards, leaving you with serious downtime.
jMyles 12y ago
It runs out that these suggestions were premature, the patch released earlier today DOES NOT fix the problem. https://bugzilla.redhat.com/show_bug.cgi?id=1141597#c24 https://bugzilla.redhat.com/show_bug.cgi?id=1141597#c24 I just tested this on Ubuntu 14.04 - it's vulnerable.