Jesse Keating (jkeating@xxxxxxxxxxxxxxx) said: > As for signing packages, I do believe they are signed. Generally, in rawhide, packages are signed as follows: Key 4F2A6FD2: If they are directly inherited from: - the previous major release - updates for the previous major release Key 30C9ECF8: If they are directly inherited from: - a test release - test updates for the previous major release (shouldn't happen) Packages that don't fall into these categories will not be signed. (Historically, there have been packages signed with DB42A60E, the Red Hat key, as well. We're working on making sure this won't happen again.) Bill > > 4Suite-1.0-9.b1.i386.rpm: > Header V3 DSA signature: OK, key ID 30c9ecf8 > Header SHA1 digest: OK (c0ec735eced46931fc12e25bc96894beca6cba39) > MD5 digest: OK (6637a7c0ff8162f4e6c6ca730bd11acf) > V3 DSA signature: OK, key ID 30c9ecf8 > > > > -- > Jesse Keating RHCE (geek.j2solutions.net) > Fedora Legacy Team (www.fedoralegacy.org) > GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) > > Was I helpful? Let others know: > http://svcs.affero.net/rm.php?r=jkeating > > -- > fedora-test-list mailing list > fedora-test-list@xxxxxxxxxx > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list