Is their a more secure way to handle logwatch reports, rather than using email?

abefroman · 10-13-2009, 10:32 PM

Is their a more secure way to handle logwatch reports, rather than using email?

TIA

chrism01 · 10-13-2009, 10:41 PM

1. scp/sftp
2. pipe through gpg, then email

Probably others, depends exactly what you need eg you could have it not email and just login to look at the reports...

abefroman · 10-13-2009, 10:45 PM

Quote:

Originally Posted by chrism01

1. scp/sftp
2. pipe through gpg, then email

Probably others, depends exactly what you need eg you could have it not email and just login to look at the reports...

Thanks

I see this in the config file:

Code:

# if set, the results will be saved in <filename> instead of mailed
# or displayed.
#Save = /tmp/logwatch

Is there a way to get it to add the date to to the filename? What would the syntax be? /tmp/logwatch-%m.%d ?

chrism01 · 10-14-2009, 12:35 AM

Well, the man page http://linux.die.net/man/8/logwatch doesn't say anything, so I'd be inclined to doubt it, but you could just try it.
Alternatively, set the filename to what ever you want (as a base filename) and then let logrotate deal with it http://linux.die.net/man/8/logrotate using the dateext option in the logrotate conf.

smeezekitty · 10-14-2009, 01:01 AM

emails is pretty secure
and plenty secure for your purposes
heres a tip: do not be paranoid
they send personal information thru emails infact

JulianTosh · 10-14-2009, 03:39 AM

Quote:

Originally Posted by smeezekitty

emails is pretty secure
and plenty secure for your purposes
heres a tip: do not be paranoid
they send personal information thru emails infact

Wow. Smeezekitty, I'm really quite astonished by your assumptions.

Email is no where close to secure, by any means, and I'm sure the OP will appreciate your assigning a definition of security to his "purposes". Amazing.

OP, I think your most expedient solution is to use the save-to-file with a follow-up cron job to pgp encrypt the file and pipe to send.