Difference between revisions of "DeveloperWiki:Signing Packages"

From ArchWiki
Jump to: navigation, search
(Created page with "'''Warning: This is just a draft''' ==Create a key pair== # install <code>gnupg</code> # <code>gpg --gen-key</code> ## you may use the default options which is a 2048 Bit RSA ke...")
 
(→‎Sign your packages)
 
(27 intermediate revisions by 6 users not shown)
Line 1: Line 1:
−
'''Warning: This is just a draft'''
+
[[Category:DeveloperWiki]]__NOTOC__
 +
 
 +
==Choose a UID==
 +
* Use a valid e-mail address: no obfuscation.
 +
* The e-mail address should be reliable (do not use one you got from your ISP or a random free service).
 +
* When in doubt, you should prefer using your <code>@archlinux.org</code> address.
 +
* The UID also has to be the same as the <code>PACKAGER</code> variable you use to build packages.
 +
* A correct UID looks like this: <code>Pierre Schmitz <pierre@archlinux.de></code>
 +
* We strongly advise you use your real name. It has to be exactly that found on official documents (passport, driver's license, etc.); see [http://wiki.cacert.org/PracticeOnNames CAcert's practice on names].
  
 
==Create a key pair==
 
==Create a key pair==
−
# install <code>gnupg</code>
+
# Install <code>gnupg</code>.
−
# <code>gpg --gen-key</code>
+
# Run: <code>gpg --gen-key</code>
−
## you may use the default options which is a 2048 Bit RSA key for encryption and signing which does not expire
+
## You may use the default: a never expiring 2048-bit RSA key for encryption and signing.
−
# Also create a revoke key for later use
+
# Create a revocation certificate, for use when/if your private key ever gets compromised:
−
## <code>gpg -o ~/.gnupg/pierre@archlinux.de-revoke.asc --gen-revoke pierre@archlinux.de</code>
+
## Run: <code>gpg -o ~/.gnupg/pierre@archlinux.de-revoke.asc --gen-revoke pierre@archlinux.de</code>
−
## Make sure to create a backup of this file and probably remove it from your system afterwards
+
## Make sure to store this file in a secure location (and/or encrypt it with a passphrase); then delete the plaintext version.
 +
# Backup your private key: <code>gpg --export-secret-keys pierre@archlinux.de > pierre@archlinux.de-private.asc</code>
 +
 
 +
==Recommended: Get your key signed by CAcert==
 +
# [https://www.cacert.org/index.php?id=1 Create an account on CAcert.]
 +
# Meet CAcert assurers and have them verify your official identification documents; see [http://www.cacert.org/policy/AssurancePolicy.php CAcert's assurance policy].
 +
# You will then be able to access a new part of the CAcert website and get your key signed:
 +
## Export your public key: <code>gpg --export --armor pierre@archlinux.de > pierre@archlinux.de.asc</code>
 +
## Paste the content of that file into the form on the [https://www.cacert.org CAcert website].
 +
## Save the signed key from the CAcert website and import it: <code>gpg --import <filename></code>
 +
 
 +
==Recommended: Get your key signed by other devs==
 +
# When ever you meet with another dev, sign each others' keys.
 +
# Take this seriously: never sign a key when you cannot verify the other person's identity.
 +
# See [http://www.cacert.org/policy/AssurancePolicy.php CAcert's assurance policy] for good guidelines.
  
−
==Get your key signed by CAcert==
+
==Publish your public key==
−
# Get the cacert key and import it:
+
# Send your public key to a keyserver:
−
## <code>wget https://www.cacert.org/certs/cacert.asc</code>
+
## Check your key id with: <code>gpg -k</code>
−
## <code>gpg --import cacert.asc</code>
+
## Run: <code>gpg --send-keys KEY-ID</code>
−
# Trust this key:
+
# Add your key fingerprint to your profile at https://www.archlinux.org/devel/profile/
−
## <code>gpg --edit-key gpg@cacert.org</code>
 
−
## <code>>trust</code>
 
−
## <code>>5</code>
 
−
# Export your key:
 
−
## <code>gpg --export --armor pierre@archlinux.de > pierre@archlinux.de.asc</code>
 
−
## Paste the content of that file into the form on the cacert website to get your signed public key.
 
−
# Save the signed key from the cacert website and import it
 
−
## <code>gpg --import <filename></code>
 
−
# You might want to send your new signed key to a keyserver
 
−
## Check your key id with <code>gpg -k</code>
 
−
## <code>gpg --send-keys 9741E8AC</code>
 
−
## You could also export it again for uploading it on e.g. your webspace: <code>gpg --export --armor pierre@archlinux.de > pierre@archlinux.de.asc</code>
 
−
# You should create a backup of your keys and make sure to not forget the passphrase!
 
  
−
==Verify a signed package==
+
==Be safe!==
−
# Install and trust the cacert key
+
# Create a backup of your keys and be sure not to forget the passphrase!
−
## <code>wget https://www.cacert.org/certs/cacert.asc</code>
 
−
## <code>gpg --import cacert.asc</code>
 
−
## <code>gpg --edit-key gpg@cacert.org</code>
 
−
## <code>>trust</code>
 
−
## <code>>5</code>
 
−
# Search and import the packager's key
 
−
## <code>gpg --search-keys 9741E8AC</code>
 
−
# Verify the package
 
−
## <code>gpg --verify devtools-*.pkg.tar.xz.sig</code>
 

Latest revision as of 10:37, 15 February 2012


Choose a UID

  • Use a valid e-mail address: no obfuscation.
  • The e-mail address should be reliable (do not use one you got from your ISP or a random free service).
  • When in doubt, you should prefer using your @archlinux.org address.
  • The UID also has to be the same as the PACKAGER variable you use to build packages.
  • A correct UID looks like this: Pierre Schmitz <pierre@archlinux.de>
  • We strongly advise you use your real name. It has to be exactly that found on official documents (passport, driver's license, etc.); see CAcert's practice on names.

Create a key pair

  1. Install gnupg.
  2. Run: gpg --gen-key
    1. You may use the default: a never expiring 2048-bit RSA key for encryption and signing.
  3. Create a revocation certificate, for use when/if your private key ever gets compromised:
    1. Run: gpg -o ~/.gnupg/pierre@archlinux.de-revoke.asc --gen-revoke pierre@archlinux.de
    2. Make sure to store this file in a secure location (and/or encrypt it with a passphrase); then delete the plaintext version.
  4. Backup your private key: gpg --export-secret-keys pierre@archlinux.de > pierre@archlinux.de-private.asc

Recommended: Get your key signed by CAcert

  1. Create an account on CAcert.
  2. Meet CAcert assurers and have them verify your official identification documents; see CAcert's assurance policy.
  3. You will then be able to access a new part of the CAcert website and get your key signed:
    1. Export your public key: gpg --export --armor pierre@archlinux.de > pierre@archlinux.de.asc
    2. Paste the content of that file into the form on the CAcert website.
    3. Save the signed key from the CAcert website and import it: gpg --import <filename>

Recommended: Get your key signed by other devs

  1. When ever you meet with another dev, sign each others' keys.
  2. Take this seriously: never sign a key when you cannot verify the other person's identity.
  3. See CAcert's assurance policy for good guidelines.

Publish your public key

  1. Send your public key to a keyserver:
    1. Check your key id with: gpg -k
    2. Run: gpg --send-keys KEY-ID
  2. Add your key fingerprint to your profile at https://www.archlinux.org/devel/profile/

Be safe!

  1. Create a backup of your keys and be sure not to forget the passphrase!
Retrieved from "https://wiki.archlinux.org/index.php?title=DeveloperWiki:Signing_Packages&oldid=184856"