Fedora Signing Key Plan
1. Release-Engineering obtains the security team's approval to the below plan. (completed)
2. Generate a new key for F8 and F9 stable and a separate key for testing.
3. Automatic key migration.
4. Announce the new key and details of the migration and end-user impact.
5. Push updates signed by the new key into the new repository.
6. Re-sign all existing F8, F9, update and testing packages in the repository, leaving the .iso's alone. When the re-signed content is ready, minimize contents of the old repo and put the resigned RPMS into the new repository. The minimized old repository contains only the minimal dependencies needed to upgrade to the new fedora-release. The new PackageKit required to handle key import will also be provided.
7. After the old repository is cleaned, issue a new rpm update in the new repository.
8. Fedora 10 will have its own new key.
9. The development and release of Fedora 10 will allow for consideration of better ways to handle automatic key migration.
10. Decide if the RPMS in the existing .iso's will be re-signed.