paperkey 1.3-2 source package in Ubuntu


paperkey (1.3-2) unstable; urgency=low

  * Build depend on autotools-dev and call dh with --with autotools_dev.
    This will cause the build to use updated config.{sub,guess} files
    (closes: #727487).

 -- Peter Palfrader <email address hidden>  Tue, 03 Dec 2013 19:35:18 +0100

Upload details

Uploaded by:
Peter Palfrader
Uploaded to:
Original maintainer:
Peter Palfrader
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe utils
Trusty release universe utils


File Size SHA-256 Checksum
paperkey_1.3-2.dsc 1.4 KiB 6be388ab3edf4e755380aaa541ec46428be0d1a4f2db3f5438ec0616dc920053
paperkey_1.3.orig.tar.gz 244.3 KiB 5b57d7522336fb65c4c398eec27bf44ec0aaa35926157b79a76423231792cbfb
paperkey_1.3-2.diff.gz 2.4 KiB 7ca1395665f88919390248f3275639ef2022f1a6a6ff4ee6f289924517697807

Available diffs

No changes file available.

Binary packages built by this source

paperkey: extract just the secret information out of OpenPGP secret keys

 A reasonable way to achieve a long term backup of OpenPGP (GnuPG, PGP,
 etc) keys is to print them out on paper. The reasoning behind this is
 that paper and ink has amazingly long retention qualities - far longer
 than the magnetic or optical means that are generally used to back up
 computer data.
 Due to metadata and redundancy, OpenPGP secret keys are significantly
 larger than just the "secret bits". In fact, the secret key contains
 a complete copy of the public key. Since the public key generally
 doesn't need to be escrowed (most people have many copies of it on
 various keyservers, web pages, etc), only extracting the secret parts
 can be a real advantage.
 Paperkey extracts just those secret bytes and prints them. To
 reconstruct, you re-enter those bytes (whether by hand or via OCR) and
 paperkey can use them to transform your existing public key into a
 secret key.

paperkey-dbgsym: debug symbols for paperkey