New signing key

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m
(Plan Steps)
Line 5: Line 5:
 
== Plan Steps ==
 
== Plan Steps ==
  
1. Release-Engineering obtains the security team's approval to the below plan. (completed)
+
# {{check}} Release engineering obtains the security team's approval to the plan shown below.
 
+
# {{check}} Generate a new key for F8 and F9 stable, and a separate key for testing.
2. Generate a new key for F8 and F9 stable and a separate key for testing. (completed)
+
# {{check}} Automatic key migration.
 
+
# Announce the new key and details of the migration and end-user impact. (in progress)
3. Automatic key migration. (completed)
+
# Push updates signed by the new key into the new repository.
 
+
# 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 repository 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. (in progress)
4. Announce the new key and details of the migration and end-user impact. (in progress)
+
# After the old repository is cleaned, issue a new rpm update in the new repository.
 
+
# Create new key for Fedora 10.
5. Push updates signed by the new key into the new repository.
+
# During development and release of Fedora 10, consider and create better ways to handle automatic key migration.
 
+
# Decide if the RPMS in the existing .iso's will be re-signed.
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. (in progress)
+
 
+
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.
+
  
 
== Users ==
 
== Users ==
  
 
For those that have Fedora installed on their computer [[Enabling_New_Signing_Key]] provides information on how to enable the new key.
 
For those that have Fedora installed on their computer [[Enabling_New_Signing_Key]] provides information on how to enable the new key.

Revision as of 16:25, 5 September 2008

Fedora Signing Key Plan

This page outlines the new signing key plan that the Fedora Project is in the process of implementing. The history behind the plan can be found [here] and [here]. The release engineering team can be reached in #fedora-devel (irc.freenode.org) or emailed rel-eng@fedoraproject.org.

Plan Steps

  1. Checkmark.png Release engineering obtains the security team's approval to the plan shown below.
  2. Checkmark.png Generate a new key for F8 and F9 stable, and a separate key for testing.
  3. Checkmark.png Automatic key migration.
  4. Announce the new key and details of the migration and end-user impact. (in progress)
  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 repository 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. (in progress)
  7. After the old repository is cleaned, issue a new rpm update in the new repository.
  8. Create new key for Fedora 10.
  9. During development and release of Fedora 10, consider and create better ways to handle automatic key migration.
  10. Decide if the RPMS in the existing .iso's will be re-signed.

Users

For those that have Fedora installed on their computer Enabling_New_Signing_Key provides information on how to enable the new key.