Feature #9356

Warn that Tails OpenPGP Applet can lead to encoding problems for emails

Added by sajolida 2015-05-07 16:01:44 . Updated 2015-06-18 10:14:42 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.4.1
Start date:
2015-05-07
Due date:
% Done:

50%

Feature Branch:
feature/9356-warn_openpgp_encoding
Type of work:
End-user documentation
Blueprint:

Starter:
1
Affected tool:
OpenPGP Applet
Deliverable for:

Description

When encrypting non-US-ascii characters with Tails OpenPGP Applet:

  • The received message opens well in Claws Mail
  • The received message opens well in the applet
  • The received message doesn’t open well in Icedove

This is worth being mentioned in the OpenPGP Applet documentation.

Files

0001-first-draft-for-9356-End-user-docs.patch (1227 B) emmapeel, 2015-06-07 14:25:23

Subtasks

History

#1 Updated by intrigeri 2015-05-07 16:30:48

And given we generally like to propose better solutions, instead of merely stating “thou shallt not do that!”, I guess we should point users to our email client + OpenPGP documentation, recommending to use PGP/MIME instead of PGP/inline (the latter being the only available option when using OpenPGP Applet for email).

#2 Updated by emmapeel 2015-06-07 14:25:27

Please review:

tails@git.tails.boum.org:emmapeel/tails
[branch] feature/9356-warn_openpgp_encoding

patch attached.

#3 Updated by BitingBird 2015-06-07 16:32:17

  • Status changed from Confirmed to In Progress
  • Assignee set to sajolida
  • Target version set to Tails_1.4.1
  • % Done changed from 0 to 50
  • QA Check changed from Ready for QA to Pass

Looks good, please merge :)

#4 Updated by sajolida 2015-06-08 13:44:06

  • Status changed from In Progress to New
  • Assignee changed from sajolida to emmapeel
  • QA Check changed from Pass to Info Needed

I failed to reproduce the problem: https://mailman.boum.org/pipermail/tails-dev/2015-June/009033.html

#5 Updated by intrigeri 2015-06-08 14:59:10

  • Status changed from New to In Progress
  • Assignee deleted (emmapeel)
  • QA Check changed from Info Needed to Ready for QA

(Explained again on -dev@ why it’s a real problem.. and argued that it’s worth fixing even if a reproducer can’t be trivially found.)

#6 Updated by emmapeel 2015-06-08 17:46:56

I reproduced the problem mailing with some other person. Encoding goes wrong eventually, I think on the first hop.

#7 Updated by BitingBird 2015-06-08 18:19:26

  • QA Check changed from Ready for QA to Pass

#8 Updated by intrigeri 2015-06-09 07:07:44

  • Assignee set to sajolida

sajolida, with this additional info + what dkg and I wrote on -dev@, are you willing to take this ticket back on your plate?
Or is there anything else you need?

#9 Updated by sajolida 2015-06-09 15:51:21

  • Assignee changed from sajolida to emmapeel
  • QA Check changed from Pass to Dev Needed
  • Feature Branch changed from emmapeel:feature/9356-warn_openpgp_encoding to feature/9356-warn_openpgp_encoding

There’s a bit of tails-dev vs Redmine schizophrenia going on here, sorry. I sent emmapeel some suggestions for polishing on tails-dev. I’ll check again when she tells me she had enough :)

#10 Updated by emmapeel 2015-06-09 17:17:04

  • Assignee changed from emmapeel to sajolida
  • QA Check changed from Dev Needed to Ready for QA

yeah well thanks for suggestions, phrasing is much nicer now
please review

#11 Updated by sajolida 2015-06-18 10:08:29

  • Assignee deleted (sajolida)
  • QA Check changed from Ready for QA to Pass

Super cool! I added two commits on top of your. When doing the first review I forgot to tell you that we should write full-HTML when inside a

. That means adding

around paragraphs and all that boring stuff. Otherwise the HTML and CSS of the page gets broken (very little in your case, but it’s still a good habit to take).

#12 Updated by sajolida 2015-06-18 10:14:42

  • Status changed from In Progress to Resolved