[root@soliton autoupdate]# rpm --resign autoupdate-3.1.1-1.noarch.rpm; echo
[root@soliton autoupdate]# rpm -K autoupdate-3.1.1-1.noarch.rpm
autoupdate-3.1.1-1.noarch.rpm: md5 OK
[root@soliton autoupdate]# rpm -q rpm
It doesn't even ask for my pass pharase.
I'm able to use --addsign, --resign and -K without problem in
Sorry, my mistake: frogot to set %_signature
However, I still have a few remarks:
(1) Why dont it spit out a usefull error message!
(2) Why is the macro not set to gpg by default!?
(3) It only works if I set the %_gpg_name to the key id and
not if I set it to the email or to the full name!?
(4) Why is it necessary to set all these macros in the first place!?
gpg uses the first key found by default and most users will have only one.
Moreover, I can set the default key in the gpg options. So there is
ABSOLUTELY no reason why I should have to configure rpm in order to sign
This would have saved me 30 minutes and probably it will do so for others as
well. I hate if I have to read 5 manuals to get things working which could have
worked out of the box.
1) Because there's a whole class of configuration problems that cannot be
2) Because there are pgp and pgp5 helper binaries as well and it's not
possible to set the default to gpg.
3) Because that's the argument passed to the gnupg helper binary.
4) For well known historical reasons, digital signatures could not
be included in exportable executables.
FWIW, the digital signatures for rpm are gonna change, and soon,
by implementing DSA for verification directly in rpm. All but the
El Gamal on top of the SHA1 digest are already in place ...