From Fedora Project Wiki

(adding to documentation cat)
(Minor style changes)
Line 2: Line 2:


== What is happening? ==
== What is happening? ==
All of the existing Fedora 8 and Fedora 9 released packages and updates are to be re-signed with new GPG keys.  The newly signed content will be placed in new directories on the mirrors and new fedora-release packages will be issued to the old locations signed with the old key that reference these new locations and the new GPG keys.
All of the existing Fedora 8 and Fedora 9 released packages and updates are to be re-signed with new GPG keys.  The newly signed content will be placed in new directories on the mirrors, and new <code>fedora-release</code> packages will be issued to the old locations signed with the old key that reference these new locations and the new GPG keys.


== Why? ==
== Why? ==
Fedora treats the security and trust of its users very carefully.  As such we would like to have zero doubt that the packages we offer are in fact from Fedora.  Since we cannot in good faith continue to use the previously used GPG signing key, we have created new keys.  The transition fedora-release packages (and PackageKit updates) are signed with the old key so that existing users can install them automatically given pre-existing trust in the old key.  These should be the last packages ever signed with the old keys.
Fedora treats the security and trust of its users very carefully, and we want Fedora users to have zero doubt that the packages they receive are in fact from Fedora.  Since we cannot in good faith continue to use the previously used GPG signing key, we have created new keys.  The transition <code>fedora-release</code> packages and <code>PackageKit</code> updates are signed with the old key, so that existing users can install them automatically given pre-existing trust in the old key.  These should be the last packages ever signed with the old keys.


== When? ==
== When? ==
The resigning is happening in to phases.  Phase 1 consists of resigning all of the published Fedora 8 and Fedora 9 updates and testing updates, as well as the pending updates.  Phase 2 consists of resigning all the release packages for Fedora 8 and Fedora 9.  Phase 1 is now complete and Phase 2 is progressing.  In order to get important updates to users, we are enabling the Fedora 8 and Fedora 9 update flow now that Phase 1 is done.
The re-signing is happening in to phases.  Phase 1 consists of re-signing all of the published Fedora 8 and Fedora 9 updates and testing updates, as well as the pending updates.  Phase 2 consists of re-signing all the release packages for Fedora 8 and Fedora 9.  Phase 1 is now complete, and Phase 2 is progressing.  In order to get important updates to users, we are enabling the Fedora 8 and Fedora 9 update flow now that Phase 1 is done.


== How? ==
== How? ==
A page detailing the steps involved with resigning all the Fedora 8 and 9 content exists [[New_signing_key | here]].  Efforts are being made to keep end user interaction to a bare minimum and hopefully it can be a completely seamless process to end users.
A page detailing the steps involved with re-signing all the Fedora 8 and 9 content exists [[New_signing_key | here]].  We are making every effort to keep end user interaction to a bare minimum, and hopefully it can be a completely seamless process for end users.


== What do I have to do? ==
== What do I have to do? ==
Line 18: Line 18:


== What if something goes wrong? ==
== What if something goes wrong? ==
If your update software fails along the way here are some manual steps you can take to update yourself.
If your update software fails along the way, here are some manual steps you can take to update yourself.
 
=== Install new fedora-release ===
=== Install new fedora-release ===
==== Fedora 8 ====
==== Fedora 8 ====
Line 24: Line 25:
# Verify that the package sha1sum matches 9a684ad36f4c1f49df7c569d5990d00f7da2cb9c
# Verify that the package sha1sum matches 9a684ad36f4c1f49df7c569d5990d00f7da2cb9c
# Install the package via rpm
# Install the package via rpm
# Move on to [[#Import_the_new_key | importing the new key]].


==== Fedora 9 ====
==== Fedora 9 ====
Line 29: Line 31:
# Verify that the package sha1sum matches 259165485c16d39904200b069873967e3eb5fa6e
# Verify that the package sha1sum matches 259165485c16d39904200b069873967e3eb5fa6e
# Install the package via rpm
# Install the package via rpm
# Move on to [[#Import_the_new_key | importing the new key]].


=== Import the new key ===
=== Import the new key ===
# Verify and import the new GPG key (/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-8-and-9) per [ https://fedoraproject.org/keys https://fedoraproject.org/keys ].
# Verify and import the new GPG key (/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-8-and-9) per [https://fedoraproject.org/keys https://fedoraproject.org/keys].
# Use your update tool to get and install any new updates from the new location
# Use your update tool to get and install any new updates from the new location



Revision as of 01:38, 10 September 2008

The Fedora Project recently re-signed all of its packages with a new key. Background details regarding the key change are found here. This page exists to aide users in the transition to the newly signed content and further updates for Fedora 8 and Fedora 9.

What is happening?

All of the existing Fedora 8 and Fedora 9 released packages and updates are to be re-signed with new GPG keys. The newly signed content will be placed in new directories on the mirrors, and new fedora-release packages will be issued to the old locations signed with the old key that reference these new locations and the new GPG keys.

Why?

Fedora treats the security and trust of its users very carefully, and we want Fedora users to have zero doubt that the packages they receive are in fact from Fedora. Since we cannot in good faith continue to use the previously used GPG signing key, we have created new keys. The transition fedora-release packages and PackageKit updates are signed with the old key, so that existing users can install them automatically given pre-existing trust in the old key. These should be the last packages ever signed with the old keys.

When?

The re-signing is happening in to phases. Phase 1 consists of re-signing all of the published Fedora 8 and Fedora 9 updates and testing updates, as well as the pending updates. Phase 2 consists of re-signing all the release packages for Fedora 8 and Fedora 9. Phase 1 is now complete, and Phase 2 is progressing. In order to get important updates to users, we are enabling the Fedora 8 and Fedora 9 update flow now that Phase 1 is done.

How?

A page detailing the steps involved with re-signing all the Fedora 8 and 9 content exists here. We are making every effort to keep end user interaction to a bare minimum, and hopefully it can be a completely seamless process for end users.

What do I have to do?

Apply the next set of updates you see available. Then apply any further updates you see, verifying and importing the new GPG key along the way as prompted by your update software. That's it.

Idea.png
Checking key fingerprints
Key fingerprints can be checked against https://fedoraproject.org/keys.

What if something goes wrong?

If your update software fails along the way, here are some manual steps you can take to update yourself.

Install new fedora-release

Fedora 8

  1. Download the updated and signed fedora-release package.
  2. Verify that the package sha1sum matches 9a684ad36f4c1f49df7c569d5990d00f7da2cb9c
  3. Install the package via rpm
  4. Move on to importing the new key.

Fedora 9

  1. Download the updated and signed fedora-release package.
  2. Verify that the package sha1sum matches 259165485c16d39904200b069873967e3eb5fa6e
  3. Install the package via rpm
  4. Move on to importing the new key.

Import the new key

  1. Verify and import the new GPG key (/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-8-and-9) per https://fedoraproject.org/keys.
  2. Use your update tool to get and install any new updates from the new location

Questions?

As questions come up throughout the Fedora community they will be posted and answered here. The discussion tab is also available for questions or comments.

Contact

If you wish to contact those involved with this process, you can find us on IRC on freenode network, #fedora-admin channel.