-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I'm trying to use aide now as well .. but with the default debian
config .. it produces
every day massive changes .. especially to the /var/log/* files due to
logrotate.
Any reasonable
On 11 Dec 2003, DI Peter Burgstaller wrote:
Hi there,
I'm trying to use aide now as well .. but with the default debian
config .. it produces every day massive changes .. especially to the
/var/log/* files due to logrotate.
Any reasonable settings that account for that?
Modify AIDE's
Hi list,
A few days ago, I recieved Redhat Errata Alert about Net-SNMP
package.
Vulnerability References:
http://sourceforge.net/forum/forum.php?forum_id=308015
# that security fix was announced 3 months ago, I don't know
about why Redhat release fixed-package so late ;)
Debian's
On Thu, Dec 11, 2003 at 12:44:27PM +0100, DI Peter Burgstaller wrote:
I'm trying to use aide now as well .. but with the default debian
config .. it produces
every day massive changes .. especially to the /var/log/* files due to
logrotate.
Any reasonable settings that account for that?
On Wed, 2003-12-10 at 23:26, Peter Solodov wrote:
That's the file integrity part. As for upgrades and updates, I never
install anything automatically, but I have a cron job which checks if
updates are available. And if there are, I would log on to a machine
and install new packages myself.
On 11 Dec 2003, Douglas F. Calvert wrote:
When I do the files are obviously different in the aide database and
I wondering if anyone has come up with a way to deal with these
differences.
Do you mean that new signatures don't match the ones in database? In
this case you review changes and if
On Thu, 2003-12-11 at 06:44, DI Peter Burgstaller wrote:
Hi there,
I'm trying to use aide now as well .. but with the default debian
config .. it produces
every day massive changes .. especially to the /var/log/* files due to
logrotate.
Any reasonable settings that account for that?
On Thu, 2003-12-11 at 13:24, Peter Solodov wrote:
On 11 Dec 2003, Douglas F. Calvert wrote:
When I do the files are obviously different in the aide database and
I wondering if anyone has come up with a way to deal with these
differences.
Do you mean that new signatures don't match the
* Quoting Douglas F. Calvert ([EMAIL PROTECTED]):
This is the problem. I am having trouble implementing a solution to
update the database after an upgrade and still maintain its validity.
Run aide --update right after the upgrade and
compare the output with dpkg -L of the package.
The replace
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I'm trying to use aide now as well .. but with the default debian
config .. it produces
every day massive changes .. especially to the /var/log/* files due to
logrotate.
Any reasonable
On 11 Dec 2003, DI Peter Burgstaller wrote:
Hi there,
I'm trying to use aide now as well .. but with the default debian
config .. it produces every day massive changes .. especially to the
/var/log/* files due to logrotate.
Any reasonable settings that account for that?
Modify AIDE's
Hi list,
A few days ago, I recieved Redhat Errata Alert about Net-SNMP
package.
Vulnerability References:
http://sourceforge.net/forum/forum.php?forum_id=308015
# that security fix was announced 3 months ago, I don't know
about why Redhat release fixed-package so late ;)
Debian's
On Thu, Dec 11, 2003 at 12:44:27PM +0100, DI Peter Burgstaller wrote:
I'm trying to use aide now as well .. but with the default debian
config .. it produces
every day massive changes .. especially to the /var/log/* files due to
logrotate.
Any reasonable settings that account for that?
On 11 Dec 2003, Douglas F. Calvert wrote:
When I do the files are obviously different in the aide database and
I wondering if anyone has come up with a way to deal with these
differences.
Do you mean that new signatures don't match the ones in database? In
this case you review changes and if
On Thu, 2003-12-11 at 06:44, DI Peter Burgstaller wrote:
Hi there,
I'm trying to use aide now as well .. but with the default debian
config .. it produces
every day massive changes .. especially to the /var/log/* files due to
logrotate.
Any reasonable settings that account for that?
* Quoting Douglas F. Calvert ([EMAIL PROTECTED]):
This is the problem. I am having trouble implementing a solution to
update the database after an upgrade and still maintain its validity.
Run aide --update right after the upgrade and
compare the output with dpkg -L of the package.
The replace
16 matches
Mail list logo
