OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: [discuss] Packages having bad signatures

From: Adrian Stanciu (sadycromus.ro)
Date: Mon Sep 22 2003 - 09:04:18 CDT


Vox wrote:

>On September 1993 plus 3670 days Jason Baker wrote:
>
>
>
>>Greetings all,
>>
>>I've decided to finally try and track down why urpm always thinks that
>>packages have a bad signature. I have a setup where one server
>>fmirrors the update sites, and then all the other servers install off
>>of an NFS share, to save hammering the mirrors.
>>
>>Every time I do the update, though, I get:
>>
>>The following packages have bad signatures:
>>(packages)
>>Do you want to continue installation ? (y/N)
>>
>>Is there any way to squeeze a little more detail out of urpmi, to see
>>what it doesn't like about the signatures? Could it be as simple as
>>file permissions?
>>
>>
>
> I'm betting you don't have the signatures needed in your rpm
> database or root keyring (depends on what version of urpmi you have
> installed). And the contrib packages almost always complain about
> it...signing them is an on-again-off-again thing, from what I've
> seen.
>
> Vox
>
>
>
Here is how I fixed it:
first do
export GNUPGHOME=/root/.gnupg
and then start urpmi with whatever parameters you do.

That is because cron daemon runs with HOME=/ and gnupg (which is used by
urpmi) looks for keys in $HOME/.gnupg

Another alternative is to make a link from /root/.gnupg (or where you
have the keys) to /.gnupg,
but I don't like this method.

--Adrian.