Tenho que reiniciar após atualizar o bash para evitar o shellshock?

Question

Atualizei meus sistemas para as versões mais recentes de bash (Fedora: bash-4.2.48-2.fc19.x86_64 e CentOS: bash-4.1.2-15.el6_5.2.x86_64 )

Está meramente atualizando o suficiente para evitar a exploração ou eu preciso fechar todos os terminais, reiniciar todos os serviços ou reiniciar os sistemas?

    

Answer 1

De Perguntas frequentes sobre RedHat : (vulnerabilidade CVE-2014-6271 no Bash.)

Do I need to reboot or restart services after installing this update?

No, once the new bash package is installed, you do not need to reboot or restart any services. This issue only affects the Bash shell during startup, not already running shells. Upgrading the package will ensure all new shells that are started are using the fixed version.

    

Answer 2

Você pode precisar reiniciar alguns serviços.

De artigo do RedHat :

Do I need to reboot or restart services after installing the update for CVE-2014-6271 and CVE-2014-7169?

If your system uses exported Bash functions, restarting affected services is recommended. Affected interactive users may have to re-login, and screen or tmux sessions may need to be restarted.

The Bash update provided to fix these issues changes the names of exported functions in the environment. If a function is exported by the old version of Bash, it is not recognized by newly started Bash processes after the update, and essentially becomes undefined. Restarting the services ensures that the new version of Bash exports functions under the expected name, making it visible again.

To find out which services need to be restarted (or which users have to re-login), execute the following command after updating:

$ grep -l -z '[^)]=() {' /proc/[1-9]*/environ | cut -d/ -f3

The returned PIDs belong to processes which are using the old exported function definitions in their environment. These processes must be restarted. To discover which service started a certain PID and needs restarting, on Red Hat Enterprise Linux 7, use the following command:

$ systemctl status <PID>

On Red Hat Enterprise Linux 6 and earlier, use the pstree -p or ps -axuf command and look for a particular PID.

    

Answer 3

A reinicialização pode ser necessária somente se alguém já tiver assumido o controle da sua máquina devido ao erro. Mas nesse caso, você deve reinstalar o sistema.

Se você não tem certeza, reinicie e verifique seu sistema (os logs, os possíveis rootkits, etc.).