2011/7/8 Markos Chandras <[email protected]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 08/07/2011 10:08 ??, Bjarke Istrup Pedersen wrote: >> 2011/7/7 Markos Chandras <[email protected]>: >> On 07/07/2011 10:57 ??, Bjarke Istrup Pedersen wrote: >>>>> I'm having a problem signing manifests from time to time (it's random >>>>> if it works or not). >>>>> >>>>> When I run repoman commit, sometimes it asks for my password, and >>>>> signs it just fine. >>>>> But sometimes it just fails silently with the following error: >>>>> >>>>> You need a passphrase to unlock the secret key for >>>>> user: "Bjarke Istrup Pedersen <[email protected]>" >>>>> 1024-bit DSA key, ID 14576049, created 2008-08-20 >>>>> >>>>> gpg: cancelled by user >>>>> gpg: no default secret key: Operation cancelled >>>>> gpg: ./Manifest: clearsign failed: Operation cancelled >>>>> !!! !!! gpg exited with '512' status >>>>> !!! Disabled FEATURES='sign' >>>>> >>>>> Does anyone have an idea of why it fails to sign it randomly? >>>>> >>>>> /Bjarke >>>>> >> What happens if you edit your ~/.gnupg/gpg.conf and add >> >> default-key 14576049 ? >> >>> Hey again, >> >>> Nope, that doesn't do it, it still fails with the error: >> >>> gpg: cancelled by user >>> gpg: no default secret key: Operation cancelled >>> gpg: ./Manifest: clearsign failed: Operation cancelled >> >>> What puzzles me is why it is random if it asks for my password and >>> signs it or not. >> >> >>> >>> > You can try to setup keychain[1] so you only have to type your password once > > [1]http://www.gentoo.org/doc/en/keychain-guide.xml > - --
I've tried that, it still does not work. Even if I just login as myself and do something like this: gurligebis@raven ~ $ echo "blah" > test gurligebis@raven ~ $ gpg -n --sign test You need a passphrase to unlock the secret key for user: "Bjarke Istrup Pedersen <[email protected]>" 1024-bit DSA key, ID 14576049, created 2008-08-20 gpg: cancelled by user gpg: no default secret key: Operation cancelled gpg: signing failed: Operation cancelled I cannot figure out why gpg insists that I have cancelled anything, when it by itself fails silently. Any ideas? :) > Regards, > Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.17 (GNU/Linux) > > iQIcBAEBCgAGBQJOFrfTAAoJEPqDWhW0r/LCYhwQALCPT6+j3K4/YxlpgR16IBwm > 2tu9OCvPqXzhiirNyfjUGZBjyufwRiAq0EIyohKjrFuPXV5MOd+kBT5nxxM7ptlQ > 3lrnYobm7ccIPDXRuNfwg176nzJEa9r+dhoWBFi3x3vzBuWDVDJ2nyH9QLhGm+0G > wrxpNn5twu4kfrfXW1iCSxD+rHFzmdVawEBMPJMflxquInH4DT+qIRZGTk20BXQz > KvxS2F+5QWhSCfg7uo0M+hB+yRau41jE4vuGRD7sl2xclw1emldP8RJ/020RYj85 > b3ZdsMWK8MUfgoR7gtL3eVR8Lk/HWrCK1QoczT9rcXx1Guei9nGlkc6673pNfphl > PGE+MiH0EKS80oUW57beT0VqnryTdyDfGOtrE58nw4nm9WyDEbnJTZRBAIPFNGBA > 1d7OPaM/XiuvyIv37x/5Z5zjqSgvJMkmcxf1AtQz1rpXoeEU6kEcP2pwcSx3fi1m > uIiYm2MGS1oCzFEPN8F/ZZ0/Pt3GGWsqukNPf4bC/6VLLVsMxbHBzmurma22oB9B > T/3ESOglow3kS7Cqvzj55rt+GIZynLNSCPyvh8NCzanSNdlZUktpEpmAj9TmKSRM > XUUZv/reR1TXrFcQUkHtLczrerroqcq/fP30qqqABsckxtDJRwnAY/LPA0YMcy6H > cYuRRDC4UPlLtb3PF9PM > =1IbZ > -----END PGP SIGNATURE----- > >
