Issue 5864 in k9mail: PGP/MIME

[k9m...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Product-k9mail

New issue 5864 by msebald1...@googlemail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Feature request: Please integrate PGP/MIME to K-9 Mail as suggested here
and on the following comments:
https://code.google.com/p/k9mail/issues/detail?id=13#c68

Comparing to PGP/INLINE it is the modern way to handle PGP on email
messages. All modern mail clients handle it.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[k9m...@googlecode.com]

Comment #1 on issue 5864 by schubert...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Please, please implement this. So many forum entries all over the Internet
of people being unable to use K9 for their encrypted mails.

[k9m...@googlecode.com]

Comment #2 on issue 5864 by schubert...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I have added a small bounty on bountysource.com

https://www.bountysource.com/issues/815255-pgp-mime

You are invited to add to my pledge or claim the bounty if you solved the
issue.

[k9m...@googlecode.com]

Comment #3 on issue 5864 by andiglu...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

pgp support is the one reason why people K-9 Mail! But if it's not
supporting MIME - what is standard for the most php applications around
it's not usable.

[k9m...@googlecode.com]

Comment #4 on issue 5864 by andiglu...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

pgp support is the one reason why people will use K-9 Mail! But if it's not

[k9m...@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 13

Comment #5 on issue 5864 by bernhard...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

we are going to track the status of pgp/mime at the main bug report (Issue
13) because it is easier and alot of people follow the old issue.

[k9m...@googlecode.com]

Updates:
Status: New
Mergedinto:

Comment #6 on issue 5864 by bernhard...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

*UPDATE* this issue will be used to track the status of PGP/MIME in k9.

[k9m...@googlecode.com]

Updates:
Labels: GPG

Comment #7 on issue 5864 by bernhard...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

(No comment was entered for this change.)

[k9m...@googlecode.com]

Comment #8 on issue 5864 by BGVaug...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

APG doesn't seem to be actively developed any longer, though there are some
forks floating around. However, the Guardian Project is actively working on
a GnuPG client for Android, and they've definitely got K-9 integration in
their plans.

https://guardianproject.info/2013/05/09/gnupg-for-android-progress-we-have-an-app/

[k9m...@googlecode.com]

Comment #9 on issue 5864 by greifswa...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

As I posted in another thread, the guradian developers would like to see
PGP/MIME support in K9-Mail as well. They also would provide help for
implementing it:
https://guardianproject.info/2012/03/15/adventures-in-porting-gnupg-2-1-x-to-android

Is there anything people like me, who have no programming skills could do
to help implementing it? Should we raise some money?

[k9m...@googlecode.com]

Comment #10 on issue 5864 by oligas...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

At the moment, GnuPG on Android is lacking an API [1] which can be used by
other apps such as K9.

To implement PGP/MIME the programming needs to take place mainly on K9's
side (storing headers, detected PGP/MIME, extracting encrypted attachments
and decrypting them). In the short therm (at least until GnuPG does not
provide an API via Intents) it might be more viable to use APG's
functionality. GnuPG will definitely be more useful in the long term.

#2 posted a link [2] to raise some money for solving this issue.

[1]
https://guardianproject.info/2013/05/09/gnupg-for-android-progress-we-have-an-app/
[2] https://www.bountysource.com/issues/815255-pgp-mime

[k9m...@googlecode.com]

Comment #11 on issue 5864 by domsch...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I am developing a fork of APG. It's called OpenPGP Keychain.
Yesterday I released the new version 2.1 with a new API that I want to
integrate in K9Mail.

If you want to try it out:
Keychain:
https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain
API Demo:
https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain.demo

Sourcecode is on github: https://github.com/dschuermann/openpgp-keychain

I will post later to k9mail dev mailinglist for further discussion of the
API.

As oligas... said, to support PGP/MIME more work on K9Mail's side is
needed. Also see this old pull request: https://github.com/k9mail/k-9/pull/4

[k9m...@googlecode.com]

Comment #12 on issue 5864 by julian.s...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Hi everyone.
This issue is a big deal for me, so I'm willing to pay USD 50.00 for it.
This offer is registered on FreedomSponsors
(http://www.freedomsponsors.org/core/issue/346/pgpmime-support).
If you solve it (according to the acceptance criteria described there),
please register on FreedomSponsors and mark it as resolved there
I'll then check it out and gladly pay up!

Oh, and if anyone else also wants throw in a few bucks on this, you should
check out FreedomSponsors!

[k9m...@googlecode.com]

Comment #13 on issue 5864 by julian.s...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Sorry for the noise. The Freedomsponsors bounty has been removed. I moved
my money to bountysource. :)

[k9m...@googlecode.com]

Comment #14 on issue 5864 by irisundm...@googlemail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Hi everyone,
when receiving PGP/Mime we get an empty body and attachments "noname.pgp"
and "noname.". We can store and decrypt "noname." - at least in textual
cases. So why we need changes in database prior to do this by progam?

[k9m...@googlecode.com]

Comment #15 on issue 5864 by mar...@kraan.net: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

you can change Mac GPGmail to send inline. then it basicly works but i
prefer a PGP/MIME solution also

temp fix:
defaults write org.gpgtools.gpgmail UseOpenPGPInlineToSend -bool YES

[k9m...@googlecode.com]

Comment #16 on issue 5864 by sleibfa...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Could a project member give us an update on this?
Will we see a fix / enhancement?

[k9m...@googlecode.com]

Comment #17 on issue 5864 by kg4...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I'm new at android development but this functionality is so important to me
that in my free time I'm going to study the k9 code and database. I was
looking at the old thread and I though I'd comment here just to revive this
thread and put in my $.02.

It looks like this comment is at heart of the issue:
https://code.google.com/p/k9mail/issues/detail?id=13#c93 K9 parses the mail
as it comes in for display, when it does this it needs to be already
decrypted (kind-of). There are a couple of ways of handling this. 1)
Certain things in the email cannot be encrypted such as subject, from,
to... all of the header stuff. These things can be stored as as they are in
plain text in the database, everything else including the body of the email
can be stored as encrypted attachments. Looking through the code I can see
nothing that directly messes with these internally (please let me know if
I'm wrong). 2) k9 could have two databases, one for presentation and one
for stored emails. Emails could come in, be stored in it's raw format in
one database then parsed for presentation in another. Later the original
email can be retrieved from it's raw source in the first database and
decrypted.

Again, I'm new at this, though I've been in the cs field for 15+ years. Let
me know if this sounds plausible, what the issues are etc..

[k9m...@googlecode.com]

Comment #18 on issue 5864 by isildome...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I wish too that K9 would have pgp/mime implemented. I think that is a very
importante feature. K @ mail will have this feature soon.

Please don´t give up on this matter.

Thank you all.

[k9m...@googlecode.com]

Comment #19 on issue 5864 by colAfl...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Two older, partly working, attempts to support PGP/MIME in K9mail. Probably
a good point to start if somebody wants to implement PGP/MIME.

https://github.com/k9mail/k-9/pull/4
https://groups.google.com/forum/#!topic/k-9-mail/1c-O9c7_fn4

http://www.mailinglistarchive.com/html/k-9-...@googlegroups.com/2011-03/msg00122.html
https://evolvis.org/frs/shownotes.php?release_id=385
https://evolvis.org/frs/?group_id=115&release_id=385

[k9m...@googlecode.com]

Comment #20 on issue 5864 by colAfl...@gmail.com: PGP/MIME

http://code.google.com/p/k9mail/issues/detail?id=5864

Two older, partly working, attempts to support PGP/MIME in K9mail. Probably
a good point to start if somebody wants to implement PGP/MIME.

https://github.com/k9mail/k-9/pull/4
https://groups.google.com/forum/#!topic/k-9-mail/1c-O9c7_fn4

http://www.mailinglistarchive.com/html/k-9-...@googlegroups.com/2011-03/msg00122.html
https://evolvis.org/frs/shownotes.php?release_id=385
https://evolvis.org/frs/?group_id=115&release_id=385

Please also consider, that simply read-only support for PGP/Mime would
already be a great step!!!

The common everyday situation when I get frustrated about not having
PGP/Mime support is, when I receive a PGP/Mime mail. In opposite, when
writing an E-Mail, most of the time it's totally OK for me to use
PGP/Inline.

[k9m...@googlecode.com]

Comment #21 on issue 5864 by colAfl...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Three older, partly working, attempts to support PGP/MIME in K9mail.

Probably a good point to start if somebody wants to implement PGP/MIME.

https://github.com/k9mail/k-9/pull/4
https://groups.google.com/forum/#!topic/k-9-mail/1c-O9c7_fn4

http://www.mailinglistarchive.com/html/k-9-...@googlegroups.com/2011-03/msg00122.html
https://evolvis.org/frs/shownotes.php?release_id=385
https://evolvis.org/frs/?group_id=115&release_id=385

Squeaky Mail is open-source and can read PGP/Mime mails, but only in
combination with "PGP KeyRing" which isn't open-source and at least I don't
trust non-open-source software to handle my private pgp-key.
https://play.google.com/store/apps/details?id=com.imaeses.squeaky
https://github.com/imaeses/k-9
https://play.google.com/store/apps/details?id=com.imaeses.keyring.trial
https://play.google.com/store/apps/details?id=com.imaeses.keyring

[k9m...@googlecode.com]

Comment #22 on issue 5864 by vor...@versanet.de: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I absolutely support this. Being on the other side of the chain, I get
frustrated when my automatically PGP/MIME signed e-mails can't be read
by K9 users and I have to resend the e-mail, manually changed to
PGP/Inline (like this one).

Please fix this, PGP/MIME is a widely used standard for signing and
encryption.

Best regards

V.

- --
"I'm in awe, Lennier. The way you can take a straightforward, logical
proposition and turn it inside-out so that, in the end, it says what
you wanted to say instead of what it actually means. Did this come
natural or did you attend some special martial arts class for the
philosophically inclined?" -- Marcus, Babylon 5

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLaRnQACgkQ1kpoAfO+TA12iwCffWvvPF2dh4BHRUOUkb2N2G4C
VmoAnj5ELX787n8oIn3QuOB4dSZFf6EF
=d+NB
-----END PGP SIGNATURE-----

[k9m...@googlecode.com]

Comment #23 on issue 5864 by christia...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Please please let K9 understand PGP/MIME email!

Thanks!

[k9m...@googlecode.com]

Comment #24 on issue 5864 by tamarisk...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

please please add this functionality.

[k9m...@googlecode.com]

Comment #25 on issue 5864 by Cyr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Changed to Maildove, it can handle this. Fuck k9mail.

[k9m...@googlecode.com]

Comment #26 on issue 5864 by Cyr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Changed to Maildroid, it can handle this. Fuck k9mail.

[k9m...@googlecode.com]

Comment #27 on issue 5864 by colAfl...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

But using email encryption with closed source programs like Maildroid,
decreases the security significantly!

If you wan't good encryption use opensource software. Close source software
always has much higher chances of having back-doors.

[k9m...@googlecode.com]

Comment #28 on issue 5864 by Cyr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Right, but k9mail does not work for encrypted mails as you can see with
this bugreport. Which is SEVEN month old.

[k9m...@googlecode.com]

Comment #29 on issue 5864 by colAfl...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I know... :-(
I'm also quite depressed about that.

But I wouldn't switch to a closed source app because of that. If another
open source app with proper PGP/Mime support would come along, I'd use it!
But closed source just doesn't goes well with good security I think.

[k9m...@googlecode.com]

Comment #30 on issue 5864 by poh...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

The problem is that there simply exists none! I switched to R2Mail2 after I
realized this one is going to stay a 'wontfix' at least in the medium term.
Discussion has been going on for longer than 7 months about PGP/MIME.
PGP/Inline works quite messy through APG, which is not being actively
developed anymore, yet still decrypts to nonsense for non-ASCII chars
because it only supports UTF8 typeset, for instance.

[k9m...@googlecode.com]

Comment #31 on issue 5864 by isildome...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I switched to R2Mail2 too. It handles keys from Symantec Encryption
Desktop. It works perfectly. The interface is a bit old and ugly, but the
author is working on a new interface and will introduce email filters. I
gave up on K9.

[k9m...@googlecode.com]

Comment #32 on issue 5864 by meier.kr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

since R2Mail2 is not open source and I could not find a license it is just
not an option for me - both ideologically about closed source or from the
fact that closed source and security does not go together !!!

from this thread I can clearly see there is a lot of demand and there are
also people willing to work on that feature. seeing this I would like to
help out as well. and I am sure there are enough people helping with
testing.

I do not know how to get the ball rolling but I start with setting up a dev
environment on my side

[k9m...@googlecode.com]

Comment #33 on issue 5864 by schubert...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Anyone interested in getting something done about this please send me an
email to schubert....@gmail.com.

I am a bit sceptical about the possibilities at this point, but at least we
should try. Maybe a joint effort can work out the issues that need to be
solved in k9 before a proper implementation of PGP is possible.

Thankfully, git offers us the option to create forks and issue pull
requests.

It is a bit if a moonshot from my side, but let's try.

[k9m...@googlecode.com]

Comment #34 on issue 5864 by poh...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

R2Mail2 uses open source Bouncy Castle crypto API under the hood, which I
think is a much better and more comfortable approach than using some third
party provider on the device, especially if it's totally outdated like APG.

Yes, in the end it's closed source and you have to trust the developer. But
you also have to trust Google Services (which are likely to be) installed
on your phone to not spy on your keys, which I (personally) think is much
more likely to happen than R2Mail2 not being trustworthy.

Anyway, this is a decision everyone has to take for himself. I would like
to see an open source alternative available but as far as I get it,
PGP/MIME won't be supported because of the way K9 internally handles
messages (see post 3 years ago:
http://code.google.com/p/k9mail/issues/detail?id=13#c105).
R2Mail2 developer announced in a comment on Google Play that he's going to
be the first to implement PGP/MIME if K9 community succeeds in fixing those
issues!

[k9m...@googlecode.com]

Comment #35 on issue 5864 by konnisch...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I'd like to audit the amount of work that needs to be done for this and
than maybe do it in a joint effort with others.

Anyone willing to invest some time please email me
schubert....@gmail.com

[k9m...@googlecode.com]

Comment #36 on issue 5864 by schubert...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

*then

[k9m...@googlecode.com]

Comment #37 on issue 5864 by schubert...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I'm referring to changing the way PGP stores messages. I realize this is a
crucial foundation for any further work on PGP.

Also, *then

[k9m...@googlecode.com]

Comment #38 on issue 5864 by meier.kr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I am sure once k9 figured a way to store the attachment of messages in a
way to verify the signatures and/or decrpyt them, another PGP like
gnu-privacy guard or bouncy-castle it not a big deal to implement.

since I am not using google services there is no way for corporate spying
on my machine.

[k9m...@googlecode.com]

Comment #39 on issue 5864 by domsch...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Please keep in mind that we are already working on a better OpenPGP app
forked from APG. It now has a better API and last week I started again
working on k-9mail integration. So if you like to contribute consider our
project at https://github.com/openpgp-keychain/openpgp-keychain
Many issues are waiting for implementors ;)

We were also just accepted as a Google Summer of Code project:
https://github.com/openpgp-keychain/openpgp-keychain/wiki/Google-Summer-of-Code

[k9m...@googlecode.com]

Comment #40 on issue 5864 by meier.kr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

:))

I only want to get the ball rolling since a lot of people (including
myself) are longing for this feature. any issue in mind which looks like
good starting point to get into the openpgp-keychain project ?

[k9m...@googlecode.com]

Comment #41 on issue 5864 by domsch...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Hmmm there are many missing features and bugs ;)
Simply follow the guidelines here:
https://github.com/openpgp-keychain/openpgp-keychain#contribute-code

[k9m...@googlecode.com]

Comment #42 on issue 5864 by domsch...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

For more information about the current state in k9mail regarding MIME, see
ckettis comments in https://github.com/k9mail/k-9/pull/408

[k9m...@googlecode.com]

Comment #43 on issue 5864 by meier.kr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I followed that PR and the point it clear that the storage needs to change,
the part of the code I had a look at today.

[k9m...@googlecode.com]

Comment #44 on issue 5864 by gurub...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Inline PGP should be considered harmful from a security point of view:
https://dkg.fifthhorseman.net/notes/inline-pgp-harmful/

[k9m...@googlecode.com]

Comment #45 on issue 5864 by colAfl...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Sorry for that, but why does the storage-format need to be changed?


PGP/MIME should be implemented in a way, where the stored email isn't
changed at all when it's opened and decrypted.
When opening an encrypted email it should only be decrypted for viewing,
but the persistent copy shouldn't be changed and should still be encrypted
afterwards. That's exactly the way Thunderbird/Enigmail and other PGP
mailer handle it.

Same for writing. The encrypted mail should be saved in persistent storage
exactly as it's being send => encrypted!


If I currently get an PGP/MIME email using K9Mail, the encrypted part is an
attachment named "msg.asc". So everything needed is there! All left to do
is to automatically open that attachment and process it through APG.

Actually that's exactly what I'm currently doing in a manual way:
I'm opening "msg.asc" with a text-editor and copy-paste the content into
APG => "Decrypt Message". Works fine for PGP/MIME mails!
It just takes too much time for daily mail reading and is too difficult for
somebody who's not IT professional.

If writing PGP/MIME mails is more difficult to implement, don't worry! What
we need is to be able to read PGP/MIME. To be able to write PGP/MIME from
Android devices has much lower priority.

[k9m...@googlecode.com]

Comment #46 on issue 5864 by julian.s...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Hey,

just as a reminder: there is a bounty out for this issue.

https://www.bountysource.com/issues/815255-pgp-mime/bounty

Julian

[k9m...@googlecode.com]

Comment #47 on issue 5864 by domsch...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

@colAfl...

Please read ckettis comment:
https://github.com/k9mail/k-9/pull/408#issuecomment-34895593

"In order for this to work we need to be able to reconstruct a
byte-identical copy of this message part."

[k9m...@googlecode.com]

Comment #48 on issue 5864 by christia...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Sorry, i am a little fed up with this issue, so i want to put it mildly:

Why the f*** is there any need to "reconstruct" a "byte-identical" copy of
the message _at_ _all_? It just should not touch any parts of the MIME
encoded message structure.

Mail-handling does not have to be reinvented, there are
several "byte-identical" storage formats out there (Maildir,MH and MBOX
come to mind)

Even my Mutt does it right (and has been doing so for quite some time now)

Actually if you only want to see the contents of an encrypted text email
(PGP/MIME encoded) you can pipe the bare file through gpg and will get a
half-way decent result

If i want to check a signature i can do that later on using a different
mailer.

But i want to be read to read that email now - here - on my phone.

[k9m...@googlecode.com]

Comment #49 on issue 5864 by domsch...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

@christia...@gmail.com

lol, chill out...

This is still an open source project, if you want to have this fixed
communicate with cketti and code it.

[k9m...@googlecode.com]

Comment #50 on issue 5864 by colAfl...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I think christia...@gmail.com is right (but he actually could calm down a
little).

People are starting to leave K9Mail for other email clients like R2Mail2,
because of the lack of PGP/MIME support. And I'm a great fan of doing it
the right way and solving basic problems like a bad storage format. But if
that needs too much time, it's better to have some workaround first.

And, as I said, don't care about writing PGP/MIME email. And also don't
care about checking signatures. What's urgently needed is the possibility
to read PGP/MIME encrypted emails!

[k9m...@googlecode.com]

Comment #51 on issue 5864 by isildome...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I just want to say that Maildroid works with PGP/MIME, too. It works
together with another free app (Crypto Plugin) from the same developer,
where we manage our PGP keys. I just tested and it works perfectly.

K9Mail, bye, bye.

[k9m...@googlecode.com]

Comment #52 on issue 5864 by andrew.w...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

I had a look but is doesn't look like Maildroid is Free Free, just you
don't pay for it.

Most peole who want PGP/MIME aren't going to trust non-free software to
do it for them, including myself.

[k9m...@googlecode.com]

Comment #53 on issue 5864 by isildome...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Do you trust Google, Facebook, Twitter, Yahoo? Are you 100% shure that your
emails are safe?
You have your personal information spread around the world, and you don't
trust this little program? I just don't understand this. Unless you are a
developer to see if is anything wrong with the code, you don't know
nothing, too.

[k9m...@googlecode.com]

Comment #54 on issue 5864 by bob.igo....@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

_He_ doesn't have to be a developer. _He_ just has to realize that other
developers will look at the code, and that it's harder to hide malicious
code in the open.

[k9m...@googlecode.com]

Comment #55 on issue 5864 by meier.kr...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

bruce schneier started to call it

insecurity by obscurity

https://www.schneier.com/blog/archives/2014/02/the_insecurity_2.html

I use encryption since I do not trust google, yahoo, microsoft, apple, etc
and with encryption I can hide a big portion (not the metadata) from them.
since k-9 mail is open source is will be the choice over any "just trust
me" app with closed source.

[k9m...@googlecode.com]

Comment #56 on issue 5864 by isildome...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Like Symantec PGP Encryption? Should we trust him?

[k9m...@googlecode.com]

Comment #57 on issue 5864 by 1gravity...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Time to un-star this issue as some people are too stupid to understand that
this isn't a discussion forum

[k9m...@googlecode.com]

Comment #58 on issue 5864 by isildome...@gmail.com: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

Well, I can't wait for another 7 months just to see people asking for
K9Mail to implement PGP/MIME. So, I will just assume that PGP/MIME will not
be implemented soon. Of course that when that happen, I have no problems to
back to K9Mail. It's an excelent email app.

[k9m...@googlecode.com]

Updates:
Status: Accepted
Labels: -Type-Defect Type-Enhancement

Comment #59 on issue 5864 by cketti: PGP/MIME
http://code.google.com/p/k9mail/issues/detail?id=5864

FYI: https://groups.google.com/forum/#!topic/k-9-dev/ibSwkJVYTU0

Sadly, such a remark seems to be necessary: Please refrain from commenting
unless you have useful information to add.

[k9m...@googlecode.com]

Comment #60 on issue 5864 by michael....@network.rca.ac.uk: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Just started working on a project that requires secure communication.
Clients send PGP/MIME and I can't just tell them to change everything on
their end. Obviously I'm able to read the e-mails on my computer, but it
would be really good to be able to read them when out of office.

So...bump. Apart from that K9 is great of course.

[k9m...@googlecode.com]

Comment #61 on issue 5864 by rickyorb...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Is this going to get looked at now that K9 is using Openkeychain?

[k9m...@googlecode.com]

Comment #62 on issue 5864 by pad...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Me too, please add PGP/MIME. OpenKeychain author says it must be
implemented on your side.

[k9m...@googlecode.com]

Comment #63 on issue 5864 by deviant....@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

PGP/MIME is the official standard means of communicating via PGP. Inline
PGP was a weird back-formation hacked-together standard that is far less
widely used.

I love OpenKeychain and it's a great tool and works better than APG, but we
do really need proper support in K9.

[k9m...@googlecode.com]

Comment #64 on issue 5864 by dsm...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

I fully agree with #45 colAfl...@gmail.com. There is no need for full GPG
feature support. And if I have to write emails using only PGP/inline that
is also OK. But I cannot tell OTHER people that THEY should use PGP/inline
just because I cannot handle PGP/MIME with K9.

For reading PGP/MIME, I currently have to save the attachment, load it into
APG, save the decrypted file, look at it in text mode. In other words, pipe
through manually. Why is it so difficult to implement these 4 steps in K9
that the issue is open for more than a year?

[k9m...@googlecode.com]

Comment #65 on issue 5864 by raphael....@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Please implement pgp/mime!

[k9m...@googlecode.com]

Comment #66 on issue 5864 by pit.schu...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Squeaky Mail, a fork of K9 has apparently implemented PGP/MIME.
http://appcrawlr.com/android/squeaky-mail

[k9m...@googlecode.com]

Comment #67 on issue 5864 by titus.st...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Squeaky Mail requires a proprietary PGP app, it seems (at least I cannot
discover the source code for "PGP Key Ring"), so those who want to rely on
Free Software cannot use it. It might still be valuable for developers to
look at the Squeaky Mail source code to see what approach they've taken.

[k9m...@googlecode.com]

Comment #68 on issue 5864 by em...@best-mac-tips.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Here's another hand up supporting the motion toward PGP/MIME support in K9.

For the record, there is another Android app I've found that claims to
support it is Maildroid (PAID). Unfortunately when it comes to decrypting
the attachments it ends in an error (on both my devices). What's more, it's
only a feature in their PAID version of the app (not the FREE version).

It truly would be great to see an open source / free option, and K9 seems
like the best way to go.

[k9m...@googlecode.com]

Comment #69 on issue 5864 by em...@best-mac-tips.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Actually, I must correct my previous message (comment #68). Maildroid
(free) does in fact have full GPG/PGP/SIME mail support. It handles
encrypted messages inline and as attachments. I've now managed to get it
working on my phone, and it works very well. It is not, however, open
source (not as far as I know). So, it would still be great to see K9 (as
the #1 open source Android mail app) to have full support for encryption as
attachments and inline.

[k9m...@googlecode.com]

Comment #70 on issue 5864 by alanthe...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

I received an email from pgp.com & was disturbed to find that I couldn't
verify it as the signature is in a file of type application/pgp-signature

I am upset that I cannot verify PGP signatures from PGP.COM

[k9m...@googlecode.com]

Comment #71 on issue 5864 by google_...@jonkers.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Bounty is now at 1K.

[k9m...@googlecode.com]

Comment #72 on issue 5864 by nbigaoue...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

I'd like to see PGP/mime implemented, as everybody.

I've had a hard time finding if any work was started on the issue so I'm
posting an update I've found.

According to this post[0] from cketti, k9 modifies the mail it receives;
the mails are parsed and converted to "'text content', 'html content' and
attachments". Some work was done in a branch[1] to change how emails are
stored. I don't know if that branch contains work on the current issue or
if it's just about the storage.

There isn't much discussion going on on the dev mailing list; any help is
probably welcomed. See "Contributing to K-9 Mail"
(https://github.com/k9mail/k-9/wiki#contributing-to-k-9-mail)

[0] https://groups.google.com/d/msg/k-9-dev/cDcnWYLnUyg/rW3UlqYxAXgJ
[1] https://github.com/k9mail/k-9/tree/pgp_mime_preparations

[k9m...@googlecode.com]

Comment #73 on issue 5864 by alanthe...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

see also - https://github.com/k9mail/k-9/commits/pgp_mime_preparations

[k9m...@googlecode.com]

Comment #74 on issue 5864 by cketti: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Issue 6756 has been merged into this issue.

[k9m...@googlecode.com]

Comment #75 on issue 5864 by bitstrea...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Wow! So many comments and this issue is still 'Medium' and 'Enhancement'
only? May I ask what the real problem is on implementing the PGP/Mime
support, that is not only supporting old fashion inline encryption? As
maintainer (openSUSE) and user of mutt I have found that there is a
workaround for mutt which simply removes the 'Content-Disposition: inline'
to break RFC 2183 but enables k9mail to handle PGP/Mime messages, see
http://markmail.org/message/4e65iabuarv2lnyo.

[k9m...@googlecode.com]

Comment #76 on issue 5864 by bitstrea...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

The mutt ticket can be found here http://dev.mutt.org/trac/ticket/3594

[k9m...@googlecode.com]

Comment #77 on issue 5864 by klaus.bi...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Given the more recent revelations about mass surveillance, this should
really be higher prioritized than "Medium", to get "my mom" to use PGP.
Believe it or not, to "normal people", not being able to use
fat/bold/italic is a deal breaker, and they would rather not use encryption
at all just to have these features.

Help me convince my mom and implement PGP/MIME! :)

Apart from that, just thanks for the awesome work you do! :)

[k9m...@googlecode.com]

Comment #78 on issue 5864 by mo...@mindsnack.net: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

You can save the encrypted agttachments, open open-key-chain or APG,
decrypt and save them and open the decrypted files with a text editor. If
this could be done automatically, I'd be happier. How can I set the apps,
that are started in "open with.." ?
I do not have an android system, just android support in Jolla Sailfish.
Maybe the next version of Sailfish - or Sailfish Secure - will have native
support for pgp mime.

[k9m...@googlecode.com]

Comment #79 on issue 5864 by a.panwin...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

I'm not shore, if I am right, but I found
Squeaky Mail

It looks as a fork from K9 (some commits behind of main) but can work with
pgp/mime

Is that correct? I favourize K9 - but if squeaky mail goes along with k9 in
the future?

[k9m...@googlecode.com]

Comment #80 on issue 5864 by brisk...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Indeed, been using Squeaky for cpl of months now, same as K9 by the looks,
and on-the-fly decryption works.

[k9m...@googlecode.com]

Comment #81 on issue 5864 by colAfl...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

"Squeaky Mail" can only handle PGP/MIME if the "PGP KeyRing" App is being
used instead of "APG".

https://play.google.com/store/apps/details?id=com.imaeses.squeaky

https://play.google.com/store/apps/details?id=com.imaeses.keyring

Unfortunately, "PGP KeyRing" isn't Open-Source and costs 1,79 EUR.


If you don't care so much about Open-Source (and costs), you can also use
R2Mail2 for PGP/MIME.

https://play.google.com/store/apps/details?id=at.rundquadrat.android.r2mail2

But I think, Open-Source is very important for trustworthy PGP encryption!

[k9m...@googlecode.com]

Comment #82 on issue 5864 by merijn....@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

aperantly Mattis Pasch patched K9 to support receiving signed/encrytped
pgp/mime back in 2011. He got it working! But since he never used github
before the patch was not accepted.

If someone who knows how to use github can just copypaste and resubmit the
patchwork he did,or create a K10 fork for all i care, then claim the 1000
Dollar bounty.

the code is right here:
https://github.com/k9mail/k-9/pull/4

[k9m...@googlecode.com]

Comment #83 on issue 5864 by bitstrea...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Seems to require more than copy and paste, nevertheless without the
interest and the help of the core upstream developers this seems to be a
dead loss, or what should I read from
https://groups.google.com/forum/#!topic/k-9-dev/ibSwkJVYTU0

[k9m...@googlecode.com]

Comment #84 on issue 5864 by berndjan...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Facebook has started on 01 Jun 2015 to optionally send encrypted status
information to its users who upload their public PGP key there (see
https://www.facebook.com/notes/protecting-the-graph/securing-email-communications-from-facebook/1611941762379302).

As I noticed when configuring encrypted status information for my facebook
account, the e-mails are then encrypted using PGP/MIME. And this is
unfortunately not understood yet by K-9 Mail.

The structure of the encrypted facebook e-mail is:
Content-Type: multipart/encrypted; protocol="application/pgp-encrypted";
The body contains two parts.

1) The first part looks like this:
Content-Type: application/pgp-encrypted; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Content-Description: PGP/MIME Versions Identification

Version: 1

2) The second part has this header:
Content-Type: application/octet-stream; name="encrypted.asc"
Content-Transfer-Encoding: 7bit
Content-ID: <0>
Content-Disposition: inline; filename="encrypted.asc"

Its body contains the PGP-encrypted message (ASCII-armoured).

My K-9 Mail client (Version 5.006 on Android 4.4) displays that there is no
message text. The "attachments" are only displayd after clicking on "more"
and are labelled "noname.pgp" and "encrypted.asc". Saving "encrypted.asc"
and opening it manually with APG allows its decryption. But then I have the
encrypted contents in MIME format outside K-9 Mail.

Please integrate also PGP/MIME into K-9 Mail. I guess this should work with
APG once K-9 Mail understands that it should send the
encrypted "attachment" there for decryption.

[k9m...@googlecode.com]

Comment #85 on issue 5864 by alanthe...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

Is K-9 going to become standards-compliant? --
http://support.gpgtools.org/discussions/problems/31985-compatibility-between-gpgtoolsopenpgp-and-android

[k9m...@googlecode.com]

Comment #86 on issue 5864 by walkw...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

If you're not going to fix this anytime soon, at least add a warning dialog
about unencrypted attachments when an email is encrypted.

[k9m...@googlecode.com]

Comment #87 on issue 5864 by Joshh...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

+1 on PGP/MIME support for K-9. I'm able to decrypt messages I receive
as "encrypted.asc" by first saving the attachment, then browsing to it
using my file manager on the phone (Solid Explorer in this case). Then I
can decrypt using APG, and then finally read the contents of the
unencrypted file in explorer's text editor.

Quite roundabout, but at least possible.

[k9m...@googlecode.com]

Comment #88 on issue 5864 by alanthe...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

It looks like K-9 has a 'milestone' for this, but no due date..
https://github.com/k9mail/k-9/milestones/PGP/MIME

[k9m...@googlecode.com]

Comment #89 on issue 5864 by alanthe...@gmail.com: PGP/MIME
https://code.google.com/p/k9mail/issues/detail?id=5864

RFC3156 is 14 years old this month. It is the standard for using PGP with
email. It describes PGP/MIME