[Fixed] GPG/enigmail broken with 3.1.7

you are right, there seems to be something fishy since the recent update.
I di dnot notice, since using 20024 for daily work still.

It looks like that somehow it tries to look for keys in somewhere appdata on c drive or so, definitely broken with the last update.

It lookks like it forces to store the keyrings to appdata gnupg and looks for them there what ever I try.
On start, it was even searching for the gpg.exe somewhere on system drive, on next start it improved, but the keyrings it refuses to accept any other position then in the appdata gnupg.
This is very problematic, if run and the keys imported again, they are copied and left on the host machine on exit.

Furtermore, it seems that the gpg.con is not read any more(??) and so settings are lost.

I would not recommend to use this version if encryption is needed.

John, can you please look into it to confirm if this is some portable problem or general some incompatibility with the enigmail?

I've posted a fix that should handle both issues:
https://portableapps.com/temp/ThunderbirdPortable.exe

Please ensure this works for you for both the \n issue and the APPDATA issue and post your results.

Both of these issues have been fixed in 3.1.7 Rev 2. Now, directories with n after a backslash will not confusing the processor and the GPG directories should be placed in the correct places.

If you attempted to create a new key with the GPG and the broken 3.17 release, any files created would be located in APPDATA\gnugpg on your PC. The exact locations vary but should be as follows:

On Vista/7: C:\Users\&ltusername>\AppData\Roaming\gnupg
On XP: C:\Documents and Settings\<username>\Application Data\gnupg

If you don't use a local copy of GPG, you can safely delete them.

Attempting to use the 3.1.7 release to sign messages should have failed and would not have transferred your existing private keys to the local machine.