From Fedora Project Wiki

(User doc for enabling new keys)
 
mNo edit summary
Line 6: Line 6:


Users will need to accept the new signing key the first time updates are downloaded. To accept the key, press 'y' when prompted whether or not to import the signing key by PackageKit.
Users will need to accept the new signing key the first time updates are downloaded. To accept the key, press 'y' when prompted whether or not to import the signing key by PackageKit.
After the new packages have been released for a period of time (not yet determined) there will be a new .rpm build that will forcibly remove the old key from the system rpmdb. This will ensure that the old key is not trusted/used by the system.
The plan for implementing the new key is very fluid, therefore changes can be expected. This page will be updated as new information is obtained.

Revision as of 17:35, 5 September 2008

The New Fedora Signing Key

The Fedora Project recently re-signed all of its packages with a new key. The story regarding the key can be found [here]. The release engineering team can be reached in #fedora-devel (irc.freenode.org) or emailed rel-eng@fedoraproject.org for more information.

Enabling the New Signing Key

Users will need to accept the new signing key the first time updates are downloaded. To accept the key, press 'y' when prompted whether or not to import the signing key by PackageKit.

After the new packages have been released for a period of time (not yet determined) there will be a new .rpm build that will forcibly remove the old key from the system rpmdb. This will ensure that the old key is not trusted/used by the system.

The plan for implementing the new key is very fluid, therefore changes can be expected. This page will be updated as new information is obtained.