Feature #8401

Improve monkeysign integration in Tails

Added by intrigeri 2014-12-06 11:39:57 . Updated 2019-06-10 14:47:40 .

Status:
Rejected
Priority:
Low
Assignee:
Category:
Target version:
Start date:
2014-12-06
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
1
Affected tool:
Deliverable for:

Description

Our initial integration of monkeysign is lacking in many ways (see parent ticket). We’ve evaluated GNOME keysign but it’s not an alternative to replace monkeysign with it. Thus we should put more work into improving monkeysign’s integration into Tails.

Before working on this, see Feature #11240 that has updates about the future (or lack thereof) of monkeysign.

Subtasks

Related issues

Related to Tails - Feature #11240: Document monkeysign Rejected 2016-03-15
Related to Tails - Feature #14581: Install caff (signing-party) by default Rejected 2017-09-01
Blocked by Tails - Feature #8400: Test & evaluate GNOME Keysign Resolved 2014-12-06

History

#1 Updated by intrigeri 2014-12-06 11:40:11

#2 Updated by Anonymous 2017-06-28 10:25:07

  • Description updated

#3 Updated by Anonymous 2017-10-03 21:20:45

As gnome-keysign covers only a very specific usecase, it cannot replace monkeysign. So we can only improve monkeysign’s integration in Tails.

#4 Updated by Anonymous 2017-10-03 21:21:29

  • Subject changed from Decide between GNOME Keysign or improving monkeysign integration to Improve monkeysign integration in Tails

#5 Updated by Anonymous 2017-10-03 21:23:50

  • Type of work changed from Discuss to Wait

I’m not sure if this is still an up-to-date request at all.

#6 Updated by Anonymous 2018-01-15 13:58:59

  • Description updated
  • Type of work changed from Wait to Research
  • Starter set to Yes

In order to make this happen, we need to research how well monkeysign works in Tails or if there are any missing features or usecases. And collect the output on this ticket.

#7 Updated by sajolida 2018-01-16 14:05:00

My user story:

I’ve been using monkeysign in Tails successfully for all my key signing.

Whenever I sign a key, I get back to Feature #11240 to copy the lenghtly command line in there. I have no feedback on the security of monkeysign when connecting to my server but I trust the monkeysign developer to not be silly and I think I checked that it does SSL as some point in the past.

I use monkeysign for that because I failed to used caff in the past and monkeysign worked for me. I don’t use monkeysign for anything else (it does key verification using some QR code, right?) because I’m really used to extensive fingerprint verification, either on paper, business card, or screen and don’t need anything else.

#8 Updated by Anonymous 2018-08-18 12:56:09

  • Description updated

#9 Updated by Anonymous 2018-08-18 12:56:51

#10 Updated by Anonymous 2018-08-18 12:57:13

  • related to Feature #14581: Install caff (signing-party) by default added

#11 Updated by intrigeri 2019-02-07 08:19:41

  • Description updated
  • Priority changed from Normal to Low

#12 Updated by sajolida 2019-06-10 14:47:40

  • Status changed from Confirmed to Rejected

We removed monkeysign in 3.14.