Feature #12254
Explicit the need of armored (instead of binary) key in WhisperBack
Start date:
2017-02-19
Due date:
% Done:
0%
Description
It seems that .pgp keys are not working with WisperBack Optional PGP key.
I’ve heard it needs .asc.
this fact should be explicit in the WhisperBack popup to add a PGP key
Subtasks
Related issues
| Related to Tails - Feature #9800: Only allow OpenPGP keys that match the provided email in WhisperBack | Confirmed | 2015-07-24 |
History
#1 Updated by mercedes508 2017-02-20 20:30:48
- Status changed from New to Confirmed
- Assignee set to alant
- Type of work changed from User interface design to Code
#2 Updated by intrigeri 2017-03-10 13:08:24
- Assignee changed from alant to mercedes508
- QA Check set to Info Needed
Note that the file extension doesn’t mean much. Is this really about armored vs. binary keys?
#3 Updated by mercedes508 2017-03-14 13:42:40
- Subject changed from Exclicit the need of .asc (instead of .pgp) key in WhisperBack to Exclicit the need of armored (instead of binary) key in WhisperBack
- Assignee changed from mercedes508 to alant
In WB, if users want to add the content of their key, if they open a binary, it’s all scrapped.
#4 Updated by alant 2017-03-20 11:17:41
- Subject changed from Exclicit the need of armored (instead of binary) key in WhisperBack to Explicit the need of armored (instead of binary) key in WhisperBack
#5 Updated by Anonymous 2018-01-16 10:11:40
- QA Check deleted (
Info Needed)
#6 Updated by Anonymous 2018-01-16 10:14:28
- Starter set to Yes
Making this ticket a starter task. The code lives here: https://git-tails.immerda.ch/whisperback/
In the popup one should simply add “armored (.asc)” in the field to attach a GPG key.
#7 Updated by Anonymous 2018-08-18 11:35:24
- related to Feature #9800: Only allow OpenPGP keys that match the provided email in WhisperBack added