I prefer plain git patches. Thanks.

That should be emitted only in verbose mode. I have verbose almost always enabled so I didn't caught it. Thanks.

I created a Differential request for this change; not sure which you prefer.

I am building on a CentOS system that comes with gnupg 2.0 and I'm trying to make an isolated test install of 2.2. It would probably work fine with the right PATH, but I thought the --with-*-pgm options might help assure the new install was used.

Multiple bugs fixed here:

Tested with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

The Documentation is installed. You can find it under Help -> Gpg4win Compendium in Kleopatras menu.

I enabled the error and did the following with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 7 (64bit) with Outlook 2010

In T3442#105339, @aheinecke wrote:

In T3442#104402, @JochenSaalfeld wrote:

1. Mails encrypted with S/MIME are stored with "No Data" in the sent EMail folder, but arrive properly at the recipients (you will recieve a readable copy, if you add yourself to the list of recipients). This Issue breaks the GpgOL Plugin after some time which is leading to the described Problem.

Fixed with 474cc15d8e331c9def298dbbfe3b99e6c8cf8035

Versions Used: Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

That is the same as a key generated from a passphrase. We have already have a task T169 for this. Thus I merge them.

What is your use case for these configure option?

@tstreibl thanks for helping with your feedback!
Please note that this issue (T3442) still has the status "testing", because we want to perform some more tests before declaring it resolved. :)

In T3442#105466, @tstreibl wrote:

Starting Outlook still bring up the "Fehler in der Benutzeroberfläche von XML von "GpgOL .....Unbekannte Office.Steuerelemente-ID: TabComposerTool" Message Box.

Sorry for my inpatience...but it's a little bit hard to understand why the above, very simple test procedure obviously isn't reproducible on your systems.

Starting Outlook still bring up the "Fehler in der Benutzeroberfläche von XML von "GpgOL .....Unbekannte Office.Steuerelemente-ID: TabComposerTool" Message Box.

tested your new .dll. Created a new email. Choosed "sign". Pasted an email adress from outlook address book into the "an" field. Outlook crashs. Took me 2 seconds to test. What the hell are you testing?

Thank you very much. Both the signed only and the encrypted mail are fully valid for me (checked on the IMAP server and with kmail) and don't contain any references to gpgolXXX.dat. This means they were correctly converted to valid PGP/MIME Mails.

Dear Andre

Thanks for the report. This is indeed badly broken. I'll work on this now.
I can reproduce and also have a reproducable crash when trying to encrypt a special folder. This must be a recent regression because I tested this some months ago and it worked fine.

Indeed this was a todo that was overlooked.

Ok for me to just have it in master. It should be fixed but is not super important imo.

Hmm. I am fine changing this for master. But for 2.2 I am nut sure. Asking on gnupg-devel?

@aa: Please do us a favor and comment only relevant stuff. The bug tracker is not chitchat. Thanks.

/*here in where I am ... we can always go down to Turing primitives and maths*/

/* what? */

This might be a reason that we got multiple reports for Kleopatra since 3.0 was released that it hangs on keylisting: https://bugs.kde.org/show_bug.cgi?id=381910

Everything works correctly but the warning message is probably too cryptic. It means that the signature could not be checked because the public key that created this signature is not found. It needs to downloaded, imported and verified. (See: https://www.gpg4win.org/package-integrity.html )
We improved the warning message with gpg4win-3.0

This means that the MAPI to MIME conversion did not happen.

Jochen could you please test this on one of our test VM's again and resolve this then?

I've added a note about this in the wiki: https://wiki.gnupg.org/TroubleShooting#Passphrase_on_the_command_line

A new binary for GpgOL can be found under: http://files.gpg4win.org/Beta/gpgol/2.0.2-beta8/ or for http://files.gpg4win.org/Beta/gpgol/2.0.2-beta8_x64/

Nagi: The third suggestion (adding "--pinentry-mode loopback" to your command) should work in that case.

This is intentional with the rationale being that users either want ascii armor for some reason for all their usecases or they don't want it.
And most users won't even know what ASCII Armor means (Adding "Armor" sounds like additional protection). So we moved this setting into configuration and renamed it.

Indeed bug in Kleo, it was always 0 in kleo. (likely created during Qt5 port) fixed with: https://commits.kde.org/kleopatra/0d53416cfbe6d8fa087887c428cdfffb13514a7d

@aheinecke Regarding closing: I'd say that we should have a test on this one and then close it for only the refocussed "send-folder problem".
Can you provide an updated gpgol.dll drop in replacement?
Some of the users in the forum may be willing to test as well.

Please use just "po:" instead of "po/NN:" as tag for future commits

I think this is resolved here. As we now have the check in the installer to warn on Vista and disable Kleo / pinentry-qt

I'm not sure why a special case should be needed -- failure to create
the .kbx should not be a failure for a decryption operation in general.

No problems, if you get struggled I am here up to go extra mile for an ideal. Regards "convenience" ... well I quite agree with Richard Stallman on the specific topic the trade off between " freedom Vs convenience" https://www.youtube.com/watch?v=CP8CNp-vksc (jump to video @1minutes, 15 seconds) ;-)

So, to protect against this attack, the client needs to do both of the following:

Here are two examples:

@werner suggests using an ephemeral home directory. this is an important point.

@justus asked for examples.

Ah well, no rules without exception.

We already have a donated machine with everything setup. This is not going to change. Twitter logon is just a convenience for many folks because there are just so many twitter accounts. And after all this is a public tracker.

Hi, Werner what are the machinery requirements required for running the VM ? I can try to squeeze my academic schedule to do it but I probably would like to change twitter login for something more 'GNU' such as https://mastodon.sdf.org/about

I don't recall, but I suppose I did. It may not have been a manual invocation, but possibly a batch job from mutt or something.