I seem to be having a small problem with something in the
logcheck.ignore file. The default setup for the logcheck package under
debian already contains this entry in logcheck.ignore to avoid reporting
this common cron job:
/USR/SBIN/CRON\[.*\]: (mail) CMD ( if \[ -x /usr/sbin/exim \]; then
Is it ok to have your GPG fingerprint publicly available?
Warren
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Fri, Sep 14, 2001 at 09:02:53PM -0500, Warren Turkal wrote:
Is it ok to have your GPG fingerprint publicly available?
It is not only OK, but encouraged. If one can confirm that your
fingerprint is valid (i.e. by calling you and saying is foo really
your fingerprint?), then it's a safe bet
On Fri, Sep 14, 2001 at 09:02:31PM -0500, Warren Turkal wrote:
Is it ok to have your GPG fingerprint publicly available?
Yes.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I seem to be having a small problem with something in the
logcheck.ignore file. The default setup for the logcheck package under
debian already contains this entry in logcheck.ignore to avoid reporting
this common cron job:
/USR/SBIN/CRON\[.*\]: (mail) CMD ( if \[ -x /usr/sbin/exim \]; then
Is it ok to have your GPG fingerprint publicly available?
Warren
On Fri, Sep 14, 2001 at 09:02:31PM -0500, Warren Turkal wrote:
Is it ok to have your GPG fingerprint publicly available?
Yes.
7 matches
Mail list logo