>>> I upgraded from 4.2.5 to 4.2.7 when running the rpm -Uvh command, I >>> received serveral warning about a v3 signature versus a v4 signature. >>> >>> I didn't see a mention in the upgrade notes, or my eyes could be worse >>> than I thought... Time to update gpg.key ? >> Don't know what to tell you. Nothing has changed here since 4.2.5 and, >> according to the rpm man page: >> >> "For compatibility with older versions of GPG, PGP, and rpm, >> only V3 OpenPGP signature packets should be configured." >> >> I have gpg configured to create V3 OpenPGP signatures (which is the >> default). >> >> What does "rpm --checksig -p shorewall-common-4.2.7-0base.noarch.rpm" >> display? > > How about 'rpm -qip shorewall-common-4.2.7-0base.noarch.rpm' ?
You can disregard this request. All Shorewall 4.2 rpms have a V4 signature. Shorewall 4.0 rpms beginning with 4.0.14 have V4 signatures. This change apparently occurred when I upgraded this system to OpenSuSE 11.0. What version of rpm are you using? My oldest RPM-based systems (OpenSuSE 10.3, Fedora 8) don't have any problems with these RPMs -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ==================================================== # rpm -qa | grep rpm rpm-4.1.1-71 warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature # # cat /etc/SuSE-release SuSE Linux 9.0 (i586) VERSION = 9.0 # This box has been running so well, I haven't updated it...sigh, something else to do on the weekend.
------------------------------------------------------------------------------
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
