From 5032af29d4a6812491d49d4fd1364d21ab7e11ea Mon Sep 17 00:00:00 2001 From: gernot Date: Thu, 5 Dec 2013 11:37:04 +0000 Subject: Added a comment: Paperkey --- .../comment_1_a14427f88c9fd8e25ad8708146bb4bff._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/design/assistant/gpgkeys/comment_1_a14427f88c9fd8e25ad8708146bb4bff._comment (limited to 'doc') diff --git a/doc/design/assistant/gpgkeys/comment_1_a14427f88c9fd8e25ad8708146bb4bff._comment b/doc/design/assistant/gpgkeys/comment_1_a14427f88c9fd8e25ad8708146bb4bff._comment new file mode 100644 index 000000000..610f9bbb6 --- /dev/null +++ b/doc/design/assistant/gpgkeys/comment_1_a14427f88c9fd8e25ad8708146bb4bff._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="gernot" + ip="85.197.15.125" + subject="Paperkey" + date="2013-12-05T11:37:02Z" + content=""" +Regarding backups, have you considered using [paperkey](http://www.jabberwocky.com/software/paperkey/) (also [in Debian](http://packages.debian.org/search?keywords=paperkey))? +It only stores a minimal amount of key data and formats it in a human-readable way. + +The result is mainly meant to be printed but `paperkey` would probably also be a good way to keep the size of QR codes down. + +I've actually recovered a key from a such a printed backup (using OCR) and it worked great thanks to line-wise checksums. +Maybe you could create paperkey PDF files with a proper OCR font through the web app? + +"""]] -- cgit v1.2.3