Re:Glibc getaddrinfo stack-based buffer overflow
by nitrogen on Tuesday February 16, 2016 @12:17PM
(#11111405)
If you have dynamically linked libc (which you should), you only need to upgrade libc and restart all network processes. [Does anyone know if systemd in pid1 calls getaddrinfo? If so, this is another good reason for a minimal pid1, as you will need to reboot]
[ Parent
| on HN ]
Re:Glibc getaddrinfo stack-based buffer overflow
by the_why_of_y on Tuesday February 16, 2016 @02:27PM
(#11112456)
No reboot needed:
man systemctl
daemon-reexec
Reexecute the systemd manager. This will serialize the manager
state, reexecute the process and deserialize the state again. This
command is of little use except for debugging and package upgrades.
Sometimes, it might be helpful as a heavy-weight daemon-reload.
While the daemon is being reexecuted, all sockets systemd listening
on behalf of user configuration will stay accessible.