3 ms·

You should also reboot to ensure no running instances of bash are vulnerable.

• sauere 12y ago
  Good point.
• cesarb 12y ago
  If I understood this bug correctly, it happens during bash's initialization. If I'm right, already running instances of bash are not vulnerable, and new instances will use the fixed executable, so no reboot would be necessary for this bug.
• bdarnell 12y ago
  The vulnerability is in bash startup; any already-running shells should be safe.
• dfc 12y ago
  $ apt-cache show debian-goodies <SNIP> checkrestart - Help to find and restart processes which are using old versions of upgraded files (such as libraries)