full-disclosure - Security Updates Without Rebooting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <90691a990511141017l46d6b72dt65290504937f1c14@mail.gmail.com>
Date: Mon Nov 14 18:18:38 2005
From: marco.ermini at gmail.com (Marco Ermini)
Subject: Security Updates Without Rebooting

On 11/8/05, Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu> wrote:
[...]
> Note that rpm will only do that if the person who packaged the updated RPM
> specified a 'postinstall' scriptlet requesting it.  So RPM *can* restart a
> daemon, but it's a function of the package, not of rpm.
[...]

Sorry for the late posting...  it's an RPM specification that RPM
package installation should perform completely unattended. Restarting
a daemon is possible in the postinstall script but it seems a task
which should be asked to the sysadmin to be performed or not (like APT
and DEB packages did - but they are NOT assumed to be performed
unattended).


Cheers
--
Marco Ermini
Dubium sapientiae initium. (Descartes)
root@...an # mount -t life -o ro /dev/dna /genetic/research
(This message is for the designated recipient only and may contain
privileged or confidential information. If you have received it in
error, please notify the sender immediately and delete the original.)