full-disclosure - Cronning Update Jobs <- really a bad idea in Portage

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: <C848AFD4-8103-11D8-AA6B-000A95A0453E@umich.edu>
From: wes at umich.edu (Wesley D Craig)
Subject: Cronning Update Jobs <- really a bad idea in Portage

On 28 Mar 2004, at 15:58, Tobias Weisserth wrote:
> There's always the issue of integrity checking. Using automatic updates
> in conjunction with AIDE or Tripwire is pointless. It ruins the 
> database
> and makes it very hard to spot unwanted changes each time an automatic
> update is done.

Might suggest that you checkout radmind:

	http://radmind.org

It allows an admin to distinguish between an integrity violation and a 
legitimate update.

:wes