Activity for Patrick Brunschwig
-
Patrick Brunschwig posted a comment on discussion Enigmail Support
If you want to decrypt a message sent to yourself you need the same private key in both email clients. Did you import they OpenPGP key you're using in Postbox to Thunderbird?
-
Sender's Autocrypt key is not imported
-
I released Enigmail 3.1.8, which fixes the issue. Autocrypt keys are now automatically imported again when needed. Using Enigmail -> Sender's Key -> Import Public Key will not work - such functionality is not intended.
-
I debugged this and found that Autocrypt doesn't work indeed on SeaMonkey. I'll fix this.
-
Sender's Autocrypt key is not imported
-
That's not how Autocrypt works. When you read a mail with an Autocrypt header, Autocrypt keys are automatically imported to a separate database, and assigned to the sender's email address. The key is only imported to GnuPG once you try to send an encrypted mail to the recipient.
-
gpgme-json looked for even when settings do not require it
-
Encryption/signing broken, when using GnuPG engine
-
Please upgrade to Enigmail 3.1.7. As I said, I fixed quite a few things that are broken in 3.1.5
-
The (calculated) trust in Enigmail should not be confused with GnuPG's owner trust. Just setting ultimate trust won't help usually. From the log provided it's difficult to tell what could be wrong because it doesn't contain much relevant information. I'd need to know the exact version of Enigmail you're using, because I recently made some relevant changes. I'd also need to know you settings. It would help a lot if you could add the 1st part of the log file containing version info and settings.
-
Enigmail processes Autocrypt headers and stores them in the same sqlite database. Can you have file on a tmpfs that are simply in RAM?
-
I would recommend that you do the key importing on the command line, and then restart Enigmail: gpg --import /path/to/your/keyfile
-
It seems that ~/.enigmail is on an NFS share? You have 2 options: 1. move ~/.enigmail to some local directory, and create a symlink from ~/.enigmail to the local directory 2. use GnuPG as crypto-engine instead of OpenPGP.js (menu Enigmail > Preferences > Crypto-Engine)
-
I just created a new release that should fix the issue. You can update to the new version via the update check in the Labs Screen (Menu Tools > Labs).
-
Thanks, I found a bug in Enigmail. I'll fix it and create a new release, probably on Thursday
-
can you attach the key for beta@com.com? It seems that the key is not valid or no longer valid.
-
You don't need to uninstall GPG Suite
-
The relevant piece that changed was Enigmail. The latest (major) update from earlier this week requires that file now.
-
I don't know what you're using on macos, but if you're using the GPG Suite then that would explain why Enigmail doesn't work. Unfortunately GPG Suite doesn't provide a component that Enigmail requires (gpgme-json). I'd recommend you install gpgOSX, which is compatible with Enigmail.
-
I just spoke to the GPG Suite developers. Unfortunately they don't provide a component that Enigmail requires (gpgme-json). I'd recommend you install gpgOSX, which is compatible with Enigmail.
-
OK, but GnuPG downloaded from gnupg.org is source code only - you can't run that. I'm interested in the distribution (e.g. gpgOSX, GPG Suite or GPG Tools, brew, etc).
-
Which distribution of GnuPG did you install?
-
You can send me an (encrypted) mail to patrick AT enigmail DOT net. My key is on keys.openpgp.org.
-
Can you attach a debug log file? (https://www.enigmail.net/index.php/en/faq-en/usage)
-
Encryption/signing broken, when using GnuPG engine
-
In order to use GnuPG with Enigmail 3.1.x, you need to have gpgme-json, a component that is part of GnuPG, but not always distributed. On windows, gpgme-json is installed by default with the latest version of gpg4win (4.2.0), make sure you install that version. On macos it depends which distribution of GnuPG you're using - I can't tell without further info.
-
Error thrown in console on reply with enigmail in epyrus
-
Nevertheless, I replaced it with Components.interfaces.
-
That's weird - I can't confirm this. Ci is globally available.Do you have any other addons installed that might have modified Ci?
-
SeaMonkey: Horizontal bar in message pane widens when moving upwards
-
fixed for next version
-
SeaMonkey: Horizontal bar in message pane widens when moving upwards
-
added support for SeaMonkey
-
Encoding issue - filter action: Encrypt to key
-
Fixed on master
-
Encoding issue - filter action: Encrypt to key
-
Which distribution are you using? Apparently some distibutions don't ship gpgme-json :-( I created a statically linked x86-64 version of gpgme-json that is available from: https://enigmail.net/download/gpgme-json
-
gpgme-json looked for even when settings do not require it
-
Actually, that's exactly what changed in this version. gpgme-json is now required if you want to use gpg. gpgme-json is a JSON wrapper around gpg, which handles a lot of the problematic aspects that you're faced with if you directly integrate gpg (which already caused several security issues in Enigmail). Therefore, if you want to use gpg, then you need to install gpgme-json. Depending on your distribution , it's either a package on its own, or it comes bundled with gpgme or libgpgme.
-
...\gpg4win\..\gnupg\bin is part of the PATH variable, that's why it's done this way. There is no function in Enigmail to look specifically in that directory. However, and that is one source of the problem is that ...\gpg4win\bin is not in the PATH variable. Thus I need to apply other methods. The strange question for me is why it's not found via the Windows Registry. What you could do is to add ...\Gpg4Win\bin to the PATH environment variable.
-
It's strange that gpgme-json.exe isn't found this way. I added now the default locations of gpg4win to search for. C:\Program Files\Gpg4win\bin C:\Program Files (x86)\Gpg4win\bin Can you try the following artifact that contains this change: https://gitlab.com/enigmail/enigmail/-/jobs/3419746174/artifacts/download?file_type=archive
-
OK, that's much more what I was hoping to see :-) The way Enigmail works is that it first searches through the PATH variable, then it checks a Windows Registry entry, and then it looks for some standard locations. The Window Registry entry should be set by gpg4win: Either HKLM\Software\Wow6432Node\Gpg4win or HKLM\Software\Gpg4win "Install Directory"="C:\Program Files (x86)\Gpg4win" Can you check if the registry entry is set? Which version of gpg4win did you install?
-
The log looks really weird ... I think that some process in Enigmail is running to early. Can you install Enigmail from the following artifact? This should make sure that there process in question doesn't run before Enigmail is ready. https://gitlab.com/enigmail/enigmail/-/jobs/3418709155/artifacts/download?file_type=archive Let me know if this fixes your issue, or otherwise attach a new log file.
-
Hmm that's weird ... it seems that I'll need to check the setup wizard. But you don't actually need the wizard to use Enigmail. Can you try to restart Epyrus and just open the about dialog without running the setup wizard, wait a few seconds and then send me that debugging log file?
-
OK, and from this point on, wait a few seconds (until your keyring is loaded) and then Enigmail should work. If it still doesn't, then you should see something in the Error Console. If you don't see anything there either, then please attach a debugg log file (via menu Enigmail > Debugging Options)
-
Aside from that though, do you have any idea how I can solve my GnuPG issue? The js implementation is very slow in comparison to GnuPG's native binary code, and having to keep my key management in sync is a PITA too. I think I found something weird. Can you try if the following works for you in "GnuPG mode": 1st open About Enigmail (menu Enigmail > About Enigmail), then afterwards Enigmail works fine with GnuPG; otherwise not.
-
I now uploaded Enigmail v3.1.1, which contains that change officially. DSA and ElGamal are considered weak, no matter how large your key is. See for example here: https://words.filippo.io/dispatches/dsa/
-
If you still can't use GnuPG, I have another solution for you: I have added an option in Enigmail (in the Crypto-Engine tab) that allows you to enable "weak keys". This will make OpenPGP.js accept DSA/ElGamal keys. You can try it from the following download: https://gitlab.com/enigmail/enigmail/-/jobs/3376496428/artifacts/download?file_type=archive
-
I just tried the installer, and it seems that you need to install some other application like Kleopatra in order to get gpgme-json.exe. I created a ticket for gpg4win for this: https://dev.gnupg.org/T6286
-
Alright, thanks. A new published version is out :-)
-
The new version of Enigmail requires GnuPG 2.2.x or newer and gpgme-json. gpgme-json is delivered with gpg4win since GnuPG 2.2.0, but for Linux you might need to install that separately.
-
I have created a new version of Enigmail that works correctly with Epyrus and uploaded it on the phoebus panel. However, since I uploaded the new version, it seems that Enigmail has disappeared from the Epyrus Exensions page.
-
I will look into it.
-
changing branch "tinyjsd-2.1-branch" to "master"
-
removed obsolete tooltup code
-
rename JsdConsole to jconsole
-
added function to insert "async function f_(){...}"
-
moved TinyJSD to Developer Tools and added gobal shortcut key
-
Home
-
Signature spoofing using partially signed emails
-
Fixed with commit 9815dbb5
-
Confirmed. Actually there is code that should prevent from this sort of attacks, but apparently it does not do what it's supposed to.
-
Download
-
old_versions
-
Download
-
old_versions
-
updates for GnuPG 2.3.4
-
unable to send or save draft, looking for non existing key
-
Download
-
old_versions
-
Download
-
Download
-
Download
-
old_versions
-
I'd recommend you first install Thunderbird 68 and make Enigmail work there. I presume that the path setting in Enigmail is wrong. Enigmail 2.2 does not contain any settings dialog, therefore you can't modify the path setting there.
-
Download
-
old_versions
-
updates for GnuPG 2.2.33
-
Download
-
old_versions
-
Download
-
old_versions
-
Download
-
Download
-
old_versions
-
Download
-
old_versions
-
updated for version 2.3.2
-
Installer doesn't work on M1 mac with big sur 11.2.3
-
Download
-
old_versions
-
The tool is called gpg, not pgp. It's the Gnu Privacy Guard (and not Pretty Good Privacy)
1 >