Hi,
It seems there is a bug with enigmail.
I have a path for portable TB like: D:\nxxxxx\....
According to my understanding, when portable TB starts, portable GPG sets the correct path in prefs.js for gpg.exe. But the path is not correct: it is something like D:\name\\.... There is only one \ after the D:. In the case of \n, it is interpreted as a CR by TB and gpg is not found. If I have another letter instead of n, it works well.
I have solved the problem by modifying ThunderbirdPortable.nsi line 384 by replacing:
FileWrite $0 `user_pref("extensions.enigmail.agentPath", "$GPGPATHDIRECTORY\gpg.exe");`
with
${StrReplace} '$1' '\' '\\' '$GPGPATHDIRECTORY\gpg.exe'
FileWrite $0 `user_pref("extensions.enigmail.agentPath", '$1') ;`
with StrReplace from http://nsis.sourceforge.net/StrRep
But it seems that ...\Other\Source directory for 3.1 is not correct. The generated portable thunderbird from nsi file does not work well for gpg since my upgrade to 3.1 (worked well with 3.0.5).
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
are you using for that?
For the 3.1 there is also different enigmail
Lot of things do not work right in 3.1, but enigmail was one which di work stright away correct on my side, provided the update for the enigmail is installed.
However I was using the standard path and any more subfolders in it.
Otto Sykora
Basel, Switzerland
But the problem is the same for TB 3.0.5 + enigmail 1.0.1 as for TB 3.1 + enigmail 1.0.2. If name of PGP is something like D:\nxxxx\..., it does not work.
I corrected it by modifying .nsi file and rebuilding TB portable.
But with TB 3.1, if I rebuild TB portable from the provided nsi file, PGP does not work well (it searches keys in C:\Doc.&Settings\user.... instead of the portable directory).
first get the proper enigmail for your TB.
For TB 3.1, the enigmail should have version 1.1.x, current is 1.1.2 AFAIK.
here mozdev link http://enigmail.mozdev.org/download/index.php
Actually I am surprised that 1.02 works, or is accepted without comments by the TB 3.1. On the other hand, the enig 1.1.x will not work with someting less then 3.1
I have dropped the 3.1 TB portable for the moment, some addons are not ready yet. But the only thing which did work from start was the enigmail. It did work correctly.
Try to use it in the default path and not any additional path changes.
Where is your gpg.exe and your keyrings placed? Are they within the TB path or outside of it?
I know that it is possible to place it to other position, but the original default was within the TB folder structure.
Otto Sykora
Basel, Switzerland
Sorry for my mistake. I used the latest one available for TB 3.1 (updated automatically by TB).
It works well with path without \n.
The problem is not related with this release; I had it before. I have problem because I have a \n in the pathname (D:\n.....), and it is not well managed by TB.
To correct it with TB 3.0.x, I modified the .nsi file (see modif in my first post) and rebuilt portable TB from this nsi file.
The problem with TB 3.1 is that if I rebuild portable TB from the NSI file, GPG does not work well (even without doing any modif. in nsi file). It seems that the Other\Source directory is not correct for TB 3.1.
Finally, I succeeded to make it work.
The problem was that I was using NSIS Portable Unicode and not ANSI!
You must use ANSI to generate correctly ThunderbirdPortable launcher.
It does not work well with Unicode... Don't know why...
I have problem Thunderbird portable + GPG enigmail
If I encrypt message to my friends enigmail always encodes using my key, not the key of the recipient. It does not help either set of rules or change options. After encoding the key theoretically mail recipient can decode it without any problems because my key was used, which is the key of the sender. I think this is a client error Thunderbird Portable
Conducted a similar experience with the normal version of Thunderbird (not portable), + + the same GPG keys. In this case the problem does not occur, the encoding is carried out smoothly mails using the keys of the recipient.
Regards
sure the enigmail, as any other gpg will encrypt to your own key too by default. That means it will encrypt to the key which is designated as the default key. This is normal and rather helpful and is so since first pgp for dos was made. The reason is that you can also read what you have written yourself.
To encrypt to a friends key, either the e-mail address used must be also one of the identities in the key, if it is not, the gpg cannot find the key.
Better and more reliable id the selection of the keys manually, that means you have to set that option first, so it is asking you each time to which key you want encrypt. The list is displayed of all your public keys and you just tick the desired one.
If you created your key on that particular copy of gpg, the key is set in the gpg.conf as the default one and thus all mails are encrypted also to it.
Otto Sykora
Basel, Switzerland
I changed the key choices for manual selection, but unfortunately all the time messages are encrypted with my key.
Example:
I'll write a message, select the encryption and signature, and give to send later. The message is encrypted and signed. After checking the message, and attempt to decode the message without problem to decrypt, so it is not encrypted key of the recipient.
regards
I understand, but this is exactly what I was trying to explain you before.
This is done so by design and is default setting. Better do not change it.
You can encrypt message to 50 recipients if you want, but one of them will be you, your own key. If you select encryption, you will be presented a list of public keys to select from.
Tick which keys the message should be encrypted to. Thats all.
The purpose is, you can read your own message.
You can not decrypt with the other recipients key, since you do not have it. So you have to encrypt to your own key as well as other keys.
Otto Sykora
Basel, Switzerland
Please, my initial problem is still there.
If my directory starts with then 'n' char, the PGP directory
is something like X:\nxxxxx and the \n is interpreted somewhere
as a return.
I solve the problem by modifying the .nsi file.
Here is my solution:
I have solved the problem by modifying ThunderbirdPortable.nsi line 384 by replacing:
FileWrite $0 `user_pref("extensions.enigmail.agentPath", "$GPGPATHDIRECTORY\gpg.exe");`
with
${StrReplace} '$1' '\' '\\' '$GPGPATHDIRECTORY\gpg.exe'
FileWrite $0 `user_pref("extensions.enigmail.agentPath", '$1') ;`
with StrReplace from http://nsis.sourceforge.net/StrRep
Is it possible to integrate this modification in PortableApps Thunderbird?
Thanks!
Please, some TB portable developer could examine my request?