User Details
- User Since
- Mar 27 2017, 4:48 PM (401 w, 1 d)
- Availability
- Available
Nov 15 2022
Sep 4 2017
Sep 1 2017
Ok, I implemented this for Inline messages. The resulting armored literal data packet is encrypted as PGP/MIME message. I'm not sure this is what we want.
Implemented --unwrap stuff, too.
Aug 31 2017
I now got something that works on MIME mail rENIG1cde116d7a3dadcd8ddd45ee1259cc62a4de9cd3. This patch leaves the original mail & decrypted version in the folder on the IMAP server.
Aug 23 2017
I just tried it w/ the current master and it works. First, it displays the upload dialog and progress bar. After a second or two a message pops up that the upload was successful and I'll get a confirmation request my mail later. Clicking Ok on the message hides both dialogs.
Aug 21 2017
I'll look into it
It's only displayed in the advanced mode. Also, what do you mean w/ no response?
Aug 15 2017
Aug 14 2017
Aug 10 2017
Most of the boilerplate was moved to autogen.sh
Generate coverage information.
Aug 9 2017
So, I had a look at the code in decrypt-data.c and proc_packets. I understand that getting gpg output the resulting in human readable way isn't possible w/o changing a lot of code.
OK, thanks. I just tied it on the console and adding --unwrap causes gpg to output the PGP packet that was encrypted. I guess this is intended but from my perspective this isn't a small change. Before a user could read his permanently decrypted mail w/o any tools, now he needs gpg the parse and display the literal data packet.
Revisited patch
You sure about that? The --nowrap doesn't seem to exist. The manpage doesn't mention it and running gpg2 with it outputs gpg: invalid option "--nowrap".
Aug 4 2017
Aug 3 2017
Aug 1 2017
Jul 28 2017
Remove use of mmap(), allow out-of-source builds.
Jul 21 2017
Jul 17 2017
Jul 5 2017
Patch submitted
Jun 29 2017
Patch was accepted into Enigmail: 5e39a44f17f9ef45fd04d3069ba5d6f3092e28d6
Jun 23 2017
Patch improved & submitted
Jun 9 2017
I didn't realize that we have a release coming up. Makes sense to postpone putting the changes into master until we're sure it doesn't break the build. Thanks for the review!
Jun 8 2017
Patch submitted
Jun 6 2017
Jun 2 2017
We already have 71 new users. The site seems to be known in the community.