Feature #8957

Include paperkey package

Added by amette 2015-02-25 18:32:23 . Updated 2015-05-12 18:43:35 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.4
Start date:
2015-05-06
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Paperkey is a software to print out OpenPGP keys in as short, readable and verifiable form as possible to make the restore much easier. Printing out keys is the perfect form of backup not only for off-line main keys.

http://www.jabberwocky.com/software/paperkey/

Tails in turn is the perfect environment for creating off-line PGP keys. It just lacks a reasonable way of backing them up. For this it would be great to have paperkey installed by default, so that the trusted live system never has to connect to the internet or even be exposed to a hard disk or USB stick that could be abused to insert malware. And then later on plugging the USB stick into an insecure machine that has paperkey installed for backup is obviously defeating the purpose. As paperkey is a small C program without any major dependencies, I hope that this is not a big issue.

Subtasks

Feature #9351: Document paperkey Resolved sajolida

100

History

#1 Updated by BitingBird 2015-02-25 21:09:58

Checked, it’s in Debian, no bug open, maintainer is weasel. Seems to make sense but I let someone who uses it confirm the ticket :)

#2 Updated by intrigeri 2015-02-26 08:53:12

I think it definitely makes sense to include paperkey to support this kind of usecases.

#3 Updated by intrigeri 2015-02-26 08:57:37

  • Status changed from New to Confirmed
  • Type of work changed from Debian to Code
  • Starter changed from Yes to No

amette, do you have any plans to work on this, or to try and find someone else to do it?

#4 Updated by amette 2015-02-27 04:52:37

I figured out how to build tails including paperkey. According to the Git merge policy page the next step would be to discuss the patch on the dev mailing list, right? Or should I just attach it here?

#5 Updated by intrigeri 2015-02-27 10:19:05

redmine@labs.riseup.net wrote (27 Feb 2015 04:52:37 GMT) :
> I figured out how to build tails including paperkey.

Wooohoo!

> According to the Git merge
> policy page the next step would be to discuss the patch on the dev mailing list,
> right? Or should I just attach it here?

Please submit it to the dev mailing list.

#6 Updated by BitingBird 2015-02-27 17:41:56

  • Status changed from Confirmed to In Progress
  • Assignee set to amette

#7 Updated by intrigeri 2015-02-28 08:40:36

  • Assignee deleted (amette)
  • Target version set to Tails_1.4
  • QA Check set to Ready for QA

#8 Updated by intrigeri 2015-02-28 08:41:01

A patch was sent to tails-dev@ yesterday: <54F0B14A.20105@amette.eu>

#9 Updated by anonym 2015-04-15 11:14:14

  • Status changed from In Progress to Fix committed
  • % Done changed from 0 to 100

Applied in changeset commit:6cf35bb001ad6cdac918f6cef0d31c00afba18f6.

#10 Updated by anonym 2015-04-15 11:28:00

  • QA Check changed from Ready for QA to Pass

#11 Updated by BitingBird 2015-05-12 18:43:35

  • Status changed from Fix committed to Resolved