> > The cron job produces this every day, but the file in question has > > permissions 0600. It seems this happens because rkhunter runs gpg as > > a user (presumably root) other than the owner of gpg.conf. > > This warning isn't issued by rkhunter but by GnuPG itself. > > This is linked to the *ownership* (and not permissions) of gpg.conf. I > would guess your file is owned by another user as yours (which is a > potential security risk), either resulting from moving this file from > another user or running gpg with sudo. >
sorry, i meant to say that the gpg file is owned by the correct user (user:user) rather than saying it has mode 600, which is clearly not relevent here :) > I get this warning when using 'sudo gpg --version', as gpg still > considers its home to be /home/user/.gnupg/ (try 'sudo echo $HOME' to > understand why). aha, thanks, i undersatnd now: I am using anacron, and restartiog it via hibernate, which was called with 'sudo hibernate', this means all the anacron jobs inherit HOME=/home/user instead of /root which causes the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
