[Enigmail] test suite failures when network is flakey

Hi Enigmail folks-- https://bugs.debian.org/954268 indicates that when the Internet connection is flakey, enigmail's tests can sometimes fail or timeout in unreliable ways. It would be great if we could update the tests so that they could cope with an unreliable network. If anyone wants to

Re: [Enigmail] moving buildscripts to python3

On Sat 2019-11-09 10:51:35 +0100, Patrick Brunschwig wrote: >> Anyway, feel free to take a look at my py3 branch, and adopt/merge what >> you like. >> >> I've uploaded something close to it to debian/experimental, so we can >> see how that turns out. > > Thanks Daniel, I'll look into it :-)

Re: [Enigmail] moving buildscripts to python3

On Fri 2019-11-08 14:04:25 +0100, Patrick Brunschwig wrote: > My aim is to require a subset of the tools required by Mozilla to build > Thunderbird - the python scripts in Enigmail were all copied from the > Mozilla build toolchain, and I never modified any of them. If the > Mozilla build tools

Re: [Enigmail] package/tests/keyObj-test.js -- why claim gpg is older than it is?

On Wed 2019-11-06 22:04:34 +0100, Patrick Brunschwig wrote: > this test is to ensure that the openpgp.js variant of the source code > is used, i.e to test the openpgp.js code. I think you should remove > the complete set of test cases as you don't ship openpgp.js. Sorry, just to be clear: what

[Enigmail] package/tests/keyObj-test.js -- why claim gpg is older than it is?

Hi Patrick-- package/tests/keyObj-test.js is failing on debian CI infrastructure (https://bugs.debian.org/944216) on the last two assertions (lines 53 and 54): 41EnigmailGpg.agentVersion = "2.2.1"; 42Assert.ok(!EnigmailGpg.getGpgFeature("export-specific-uid")); 43 44

[Enigmail] moving buildscripts to python3

Hi Patrick, all-- We're in the process of getting rid of python2 in debian. Python2 will lose upstream support in a couple months. The enigmail 2.1.3 build tooling still appears to depend on python2. Have you given any thought to porting it to python3? Is that something you have any specific

Re: [Enigmail] Future OpenPGP Support in Thunderbird

On Tue 2019-10-29 19:25:14 +0100, Werner Koch wrote: > The problem with all that is that _users demanded_ the ability to > create large keyblocks, because they went to so many key signing parties > and liked to include arbitrary data. yeah, there's always a tension between different players in

Re: [Enigmail] jsunit updates and distribution

On Wed 2019-09-18 12:11:12 +0200, john doe wrote: > Git history is paramount, locally you can do what ever you want but > rebasing/merging on what is already pushed is a no go for me. What is "pushed" ? what if it was pushed to a feature branch? what if it was sent to the mailing list for a

Re: [Enigmail] jsunit updates and distribution

On Tue 2019-09-17 18:55:53 +0200, john doe wrote: > Do you mind explaining why you are against signing commits? I'd like to understand what your proposed use case and value proposition is for signed commits. I can justify my call for signed tags -- i want to have cryptographic provenenance for

Re: [Enigmail] jsunit updates and distribution

Hi Patrick-- Thanks for your prompt fixes, i've just uploaded jsunit 0.2.2-1 to debian experimental for now. --dkg signature.asc Description: PGP signature ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes

[Enigmail] jsunit updates and distribution

Hi Patrick, and other enigmail folks-- I'm trying to sort out enigmail 2.1 for debian with tbird 68. i note that to properly test the new enigmail, i need a newer version of jsunit for the testing, so i'd like to ship that in debian too. at https://www.enigmail.net/jsunit/ i see that jsunit

[Enigmail] legacy-display part when Subject is protected shouldn't include other headers

Hi Enigmail folks-- When I send encrypted e-mail with Enigmail and i choose to protect the Subject, it inserts a text/rfc822-headers part that i've been calling "legacy-display" (we used to call it "force-display", but i think that was a misnomer, since protected-header-aware clients do *not*

Re: [Enigmail] Cannot send a message, send button doesn't work

On Wed 2018-12-05 11:51:11 +0100, Patrick Brunschwig wrote: > On 05.12.18 11:00, Jerzy Spendel wrote: >> https://sourceforge.net/p/enigmail/forum/support/thread/0023f36d6d/ > > I assume that solution I proposed at the bottom of the thread does not > help ...? for reference for people following

Re: [Enigmail] invisible attachments in Mail sent from AppleMail

On Fri 2018-11-09 17:15:17 +0100, vv01f wrote: > We periodically get emails of an organization that loves to use their > Apple products but otherwise is quite nice to be informed about. a more compact summary of the structure of the message generated by Apple Mail is here: A

Re: [Enigmail] Password dialogue always in English

On Mon 2018-10-29 22:53:44 -0400, Jean-David Beyer wrote: > On 10/29/2018 11:54 AM, Daniel Kahn Gillmor wrote: >> So the question is: how far back must it go? What would the changes >> look like if we were to write a new enigmail that depended explicitly on >> GnuPG >=

Re: [Enigmail] Password dialogue always in English

On Mon 2018-10-29 14:50:57 +0100, Werner Koch wrote: > On Sat, 27 Oct 2018 17:42, patr...@enigmail.net said: > >> but when I find older versions. You obviously can't fix this by creating >> a new release ;-). Things like "missing MDC" messages for CAST5. > > I see. I general I think it is better

Re: [Enigmail] Enigmail does not detect a failed secret key import

On Tue 2018-10-09 09:22:13 +0200, Werner Koch wrote: > On Fri, 5 Oct 2018 17:34, d...@fifthhorseman.net said: > >> I ran into this with some older versions of GnuPG (e.g. the >> heavily-patched GnuPG 2.1.18 in debian stretch) during the enigmail test > > Do you happen to know whether this is also

Re: [Enigmail] jsunit versioning (and issues with jsunit 0.2.0)

On Wed 2018-10-03 16:59:48 +0200, Patrick Brunschwig wrote: > Am 3. Oktober 2018 15:13:03 MESZ schrieb Daniel Kahn Gillmor > : >>Just to clarify: jsunit 0.2.0 does not work at all without enigmail >>installed, and the self-test that it ships with is not expected to run? >

Re: [Enigmail] jsunit versioning (and issues with jsunit 0.2.0)

On Wed 2018-10-03 08:54:35 +0200, Patrick Brunschwig wrote: > Jsunit 0.2 requires at least TB 60 and Enigmail 2.1 (master). If you > check the gitlab CI file, you'll see that I only use JSunit 0.2 for > master, but not for the 2.0-branch. thanks for the details, Patrick. Just to clarify: jsunit

[Enigmail] jsunit versioning (and issues with jsunit 0.2.0)

Hi Patrick, all-- I'm trying to maintain jsunit in debian so that we can run the enigmail test suite, and i notice that Patrick recently released jsunit 0.2.0. in jsunit 0.1.6 (what i've been using), the tests send their messaging to stdout for the most part. when i try to run the same tests

[Enigmail] improving (and testing) Autocrypt key minimization

I noticed that on the 2.0 branch of enigmail, the Autocrypt OpenPGP certificate minimization wasn't cleanly matching the expected User IDs. It also wasn't being tested. I wrote a brief series of patches that improves certificate minimization and adds it to the test suite:

Re: [Enigmail] intermittent failing subprocess test on debian infrastructure

On Thu 2018-07-12 18:24:57 -0400, Daniel Kahn Gillmor wrote: > On Tue 2018-07-10 11:27:17 -0400, Daniel Kahn Gillmor wrote: >> Enigmail is in Debian unstable as of this morning, and should be on its >> way back into debian's testing distribuation. > > One more piece o

Re: [Enigmail] failing test suites on debian infrastructure

On Tue 2018-07-10 11:27:17 -0400, Daniel Kahn Gillmor wrote: > Enigmail is in Debian unstable as of this morning, and should be on its > way back into debian's testing distribuation. One more piece of followup -- we have an intermittent failure of the test suite on debian continuous integ

Re: [Enigmail] failing test suites on debian infrastructure

On Tue 2018-07-03 08:37:46 +0200, Patrick Brunschwig wrote: > On 02.07.18 20:51, Daniel Kahn Gillmor wrote: >> If it's NS_ERROR_STORAGE_BUSY, i note that there are several different >> points where thunderbird appears to just wait 10 seconds and retry when >> sqlite is compl

[Enigmail] [Robert Luberda] [Pkg-mozext-maintainers] Bug#902253: enigmail: Incorrect Polish translation for "Sign message"

Hi Enigmail folks-- we got this message from a polish-speaking debian user. I'm not closely involved in the translation work for enigmail, but it sounds like (a) Polish needs to be fixed, and (b) it might be worth sending feedback to whichever translator did the bad change to explain what went

Re: [Enigmail] Unit Tests: do you run the Enigmail test suite? if so, please respond!

On Wed 2018-07-04 12:42:33 +0200, Patrick Brunschwig wrote: > On 03.07.18 21:36, Daniel Kahn Gillmor wrote: >> Now that we have gitlab set up, would you be interested in getting the >> gitlab continuous integration set up to run on every commit? >> >> https://git

Re: [Enigmail] Unit Tests: do you run the Enigmail test suite? if so, please respond!

On Tue 2018-07-03 08:34:05 +0200, Patrick Brunschwig wrote: > On 02.07.18 20:39, Daniel Kahn Gillmor wrote: >> * when you run the enigmail unit tests > > Regularly before pushing commits (at least every few days). > >> * on what platform(s) > > On my current mac

[Enigmail] Unit Tests: do you run the Enigmail test suite? if so, please respond!

hi all-- I was wondering whether people could identify whether they currently run the enigmail test suite regularly (e.g. on each release, or during active development or bugfixing). If you do, could you please speak up, and identify: * when you run the enigmail unit tests * on what

[Enigmail] failing test suites on debian infrastructure

I'm trying to improve enigmail's test suite coverage in debian, and i've had difficulties there. This is an attempt to document the problems i'm running into, in the hopes that someone on-list here can give me suggestions for new things to try. To be clear: i can get the tests to pass cleanly

[Enigmail] handling async errors more cleanly

i've just submitted the following minor changes to autocrypt.jsm to better handle error cases: https://gitlab.com/enigmail/enigmail/merge_requests/11 in particular, when asynchronous errors do happen, the function that hits them typically needs to bail out, rather than pushing through in

[Enigmail] clarifying autocrypt errors

Hi enigmail folks-- When an error arises in enigmail's autocrypt code, it appears to just throw "error", but that could be in one of several places. Th patch here makes error reporting a bit more detailed. It would be good to have this merged into enigmail-2.0-branch. I've requested that

[Enigmail] a reproducible enigmail .xpi

Chris Lamb of the Reproducible Builds project points out that most enigmail .xpi files contain an artifact based on the filesystem sort order of the build machine. (https://bugs.debian.org/901611) This makes it hard to reliably reproduce a bit-identical .xpi from source. Reproducible builds are

Re: [Enigmail] 2.0.5 fails "make check" due to missingMdcError (should be mdcError?)

On Tue 2018-05-22 08:05:21 +0200, Patrick Brunschwig wrote: > Releases are created on my build server for better repeat-ability, and I > may have not run it on the 2.0-branch. I'll have to fix the build script... I've just submitted a series of fixes to the test suite for 2.0 branch here:

[Enigmail] enigmail, jsunit, and e10s

Hi Enigmail folks-- i think that modern versions of enigmail should work fine with e10s ("electrolysis") builds of thunderbird. is that right? however, i note that jsunit does *not* appear to be e10s ready. i see messages like this when running the test suite: 1528150605904 addons.xpi

[Enigmail] looking for a comprehensive enigmail test suite? [was: Re: avoiding openpgp.js for enigmail in debian]

Hi Patrick! On Sat 2018-05-26 18:31:46 +0200, Patrick Brunschwig wrote: >> It'd be really great if there was a test suite that could exercise all >> the expected functionality, so i could be sure my changes don't breaking >> them. do you have anything like such a suite that i could piggyback on?

Re: [Enigmail] avoiding openpgp.js for enigmail in debian

On Sun 2018-05-27 14:12:25 -0400, Daniel Kahn Gillmor wrote: >> Run the unit tests in package. I think that almost everything covered by >> tests, except for the ASM. > > thanks, i'll make sure to run both "check" and "unit". I note that i > can'

Re: [Enigmail] avoiding openpgp.js for enigmail in debian

On Sat 2018-05-26 18:31:46 +0200, Patrick Brunschwig wrote: > Let's be fair ;). OpenPGP.js is LGPL, which is considered open source. > The fact that Debian cannot handle the way that OpenPGP.js is built does > not make it (or Enigmail) less open source, but is primarily a > Debian-issue. Yes, i

[Enigmail] avoiding openpgp.js for enigmail in debian

hi patrick and other enigmail folks-- modern enigmail (2.0+) includes a copy of openpgp.js. It does not appear to be built from source, but is instead a straight copy of a generated block of javascript from the OpenPGP.js git repo (the node/javascript community appears to have a common pattern

[Enigmail] 2.0.5 fails "make check" due to missingMdcError (should be mdcError?)

Hi all-- i've just filed this pull request to fix a problem with "make check" during a build of enigmail 2.0.5: https://gitlab.com/enigmail/enigmail/merge_requests/1 I'm a little surprised to see a signed tag that doesn't pass "make check" -- is "make check" run before every release?

Re: [Enigmail] gpgv

On Thu 2018-04-19 23:54:40 +0200, Andy Weber wrote: > The process seems to be spawned by dirmngr.exe, ptree looks like this: > > + "C:\Program Files (x86)\GnuPG\bin\dirmngr.exe" --daemon --homedir > C:/Users//AppData/Roaming/gnupg >     + dirmngr.exe (Suspended and fails to resume) >     +

Re: [Enigmail] check-trustdb speed [was: Enigmail v2.0 breaks split-gpg (Qubes OS)]

On Tue 2018-03-27 15:17:19 +0200, Patrick Brunschwig wrote: > The command line option exists for many years in GnuPG. The only new > thing is that Enigmail tries to better control when the trustdb is > checked, such that importing keys into large keyrings are quicker. For > example, my keyring

Re: [Enigmail] feedback from initial enigmail setup (using wizard)

On Thu 2018-03-08 08:34:34 +0100, Patrick Brunschwig wrote: > Interestingly, *two* usability studies have suggested that the > explanations before were insufficient. The current text is actually the > suggested text from the last usability study. i wonder how the usability studies were framed

[Enigmail] feedback from initial enigmail setup (using wizard)

Hi all-- Today i have done several trial run-throughs, thunderbird 1:52.6.0-1+b1 + enigmail 2:2.0~beta2-1 on debian testing/unstable. I have a few observations and recommendations about the setup wizard. I chose the "standard configuration (recommended for beginners)". all the recommendations

Re: [Enigmail] [ANN] Enigmail 2.0 Beta 2 available

On Thu 2018-03-01 08:29:54 +0100, Patrick Brunschwig wrote: > Sourceforge is fully operational again since at least a week. I create > all builds from my build server, which would always at first update from > git at enigmail-source>. I've

Re: [Enigmail] [ANN] Enigmail 2.0 Beta 2 available

On Wed 2018-02-28 18:35:36 +0100, Patrick Brunschwig wrote: > I'm pleased to announce the 2nd beta version of Enigmail 2.0. thanks for this work! I note that sourceforge appears to still be in disaster recovery mode, as it has been for several days. Do you have a mirror of the git repository

[Enigmail] "Initiate Autocrypt Key Transfer" should not say "Key"

In the preferences dialog of enigmail 2.0-beta1, the "Transfer Settings" tab has a button "Initiate Autocrypt Key Transfer". Autocrypt goes to great pains to avoid exposing users to the term "Key", so it seems odd to see "Key" paired with "Autocrypt" here, especially since the tab itself does not

[Enigmail] "Let subject unprotected" needs improvement

Hi there-- thanks for implementing protected headers in enigmail 2.0! this is very exciting :) The dialog box that pops up on send currnetly has one button labeled "Let subject unprotected" This doesn't sound right to my en_US ears. Some other alternatives that sound better: Leave subject

[Enigmail] compose toolbar overlay -- two "Enigmail Encryption Info" choices

I'm using enigmail 2.0~beta1-1 from debian experimental. When looking to "customize" the compose toolbar, i see two options that look pretty much identical to each other, both labeled "Enigmail Encryption Info" : it'd be good to: * make the name shorter so that it's visible/understandable

Re: [Enigmail] [PATCH] express ordered build rules

On Thu 2018-02-15 00:44:28 -0500, Daniel Kahn Gillmor wrote: > By expressing the rule to create package/buildDate.jsm as a way to > target buildDate.jsm, make will force it to happen in order. > > otherwise, parallel build processes might try to invoke the deploy > rule

[Enigmail] [PATCH] express ordered build rules

By expressing the rule to create package/buildDate.jsm as a way to target buildDate.jsm, make will force it to happen in order. otherwise, parallel build processes might try to invoke the deploy rule first. Note that if your goal is to rebuild buildDate.jsm each time you build, this changeset

Re: [Enigmail] Fwd: PGP key expires in 3 days: 0x8EE66C320E62EFA8 (it can be extended)

Hi David-- On Tue 2018-02-06 13:57:47 -0500, David wrote: > I received this in today's email. Some of the information is correct but > his main data, the expiry date, is completely incorrect. i don't know about "completely incorrect" -- but maybe his keyserver isn't syncing with others? it

Re: [Enigmail] Enigmail incorrectly complains about tz announcements

On Wed 2018-01-24 18:44:58 -0800, Paul Eggert wrote: > I recently got a bug report from one user, who says that Thunderbird > complains about this email. I can reproduce the problem by viewing the > attached email with Thunderbird 52.5.2 (64-bit) which is using Enigmail > version 1.9.9

Re: [Enigmail] Missing features for Enigmail

On Wed 2018-01-24 16:11:58 -0500, Jean-David Beyer wrote: > On 01/24/2018 10:17 AM, Neil D. Donovan wrote: >> 2) Automatic decryption of received encrypted emails to the folder on >> the email server > > If I were sending you an encrypted e-mail, I presume I wish you to be > able to read it, but I

Re: [Enigmail] Feature request: forwarding encrypted messages.

On Mon 2018-01-15 12:33:54 +0200, Lachezar Dobrev wrote: > Yes, I am using "Forward as Attachment". > Typically because I'd like to forward the attachments to the > original message too. > I almost always use explicitly the Menu item to forward the mail as > an attachment. right, i think

Re: [Enigmail] Feature request: forwarding encrypted messages.

On Fri 2018-01-12 20:43:39 +0100, Andreas Hirsch wrote: > I suppose You are mixing up 'forwarding' and 'bouncing' > > If You forward a message, the old message will be decrypted and copied > into a new message. The new message would be correct encrypted for the > new recipients. i think this

Re: [Enigmail] What does "Beware of leaking sensitive information" warning mean?

On Fri 2018-01-12 15:58:25 +0200, Lachezar Dobrev wrote: > P.S. Stripped quoted messages as they seem to produce Enigmail errors. this seems like it might be a separate issue. perhaps you could start a new thread, describing specifically what enigmail errors you're seeing when you do not strip

Re: [Enigmail] What does "Beware of leaking sensitive information" warning mean?

On Wed 2018-01-03 14:39:55 +0200, Lachezar Dobrev wrote: > Recently I've been greeted with a red warning every time I try to > reply to an encrypted message saying: > > "Beware of leaking sensitive information - partially encrypted email." > > With a Details button that shows a pop-up: > >

Re: [Enigmail] [ANN] Enigmail v1.9.9 available

Thanks very much for this work, Patrick! And thanks to Posteo and Mozilla for funding this research. On Tue 2017-12-19 08:45:29 +0100, Patrick Brunschwig wrote: > [1] > > [2]

Re: [Enigmail] enigmail 1.9.9 release?

On Sat 2017-12-16 11:54:57 +0100, Patrick Brunschwig wrote: > The release is not yet published/announced because I'm waiting for > addons.mozilla.org to get it approved, such that the majority of the > users get it simultaneously with the announcement. Ok, but i've already made it available to

[Enigmail] enigmail 1.9.9 release?

hey Patrick and other good enigmail users-- I see from git that enigmail 1.9.9 has been tagged, but i don't see it for download in either of these places: https://www.enigmail.net/index.php/en/download/source-code https://www.enigmail.net/index.php/en/download I do note that the tarball

Re: [Enigmail] On Displaying Signatures

On Fri 2017-11-10 18:37:08 +0100, Patrick Brunschwig wrote: > On 10.11.17 16:25, Daniel Kahn Gillmor wrote: >> How does the user know where the first part ends and the second part >> begins? > > There's a horizontal line between every MIME part. very subtle :(

Re: [Enigmail] On Displaying Signatures

On Fri 2017-11-10 11:12:21 +0100, Patrick Brunschwig wrote: > That's a very important point. Option B is not possible without hacking > deeply into Thunderbird - I would not know how to go that way. :( > I think the following variant of A is a good compromise: > > If the *first* displayed MIME

Re: [Enigmail] On Displaying Signatures

On Thu 2017-11-09 16:30:45 +0100, Werner Koch wrote: > On Mon, 6 Nov 2017 11:46, whi...@posteo.net said: > >> Why not display exactly what GnuPG reports concerning a signature? Leave >> it up to the user to make his own value judgments. > > That is what I was about to reply ;-). > > In fact we

Re: [Enigmail] On Displaying Signatures

Hi Patrick-- Thanks for documenting this. On Sun 2017-11-05 12:06:54 +0100, Patrick Brunschwig wrote: > We *only* display signature information if *all* of the following > conditions are satisfied: One thing not covered by this discussion is how enigmail will deal with signatures that do not

Re: [Enigmail] [PATCH] autocrypt: type should always come first and addr should not, have quotes

On Mon 2017-09-25 08:24:51 +0200, Patrick Brunschwig wrote: > On 22.09.17 16:36, Karissa McKelvey wrote: >> From 93ae4c9f49fedeead1b6dd80a31f325a6fba5d30 Mon Sep 17 00:00:00 2001 >> From: okdistribute >> Date: Fri, 22 Sep 2017 16:07:17 +0200 >> Subject: [PATCH] autocrypt:

Re: [Enigmail] U+2705 HEAVY WHITE CHECK MARK (for key import)

On Thu 2017-07-06 08:23:00 +0200, Patrick Brunschwig wrote: > On 05.07.17 22:04, Daniel Kahn Gillmor wrote: > >> i see the use of unicode code point U+2705 (HEAVY WHITE CHECK MARK) in >> importInfoSuccess as broken with some font sets. [...] > I think I better replace

Re: [Enigmail] ALLOW PASTING

On Thu 2017-07-06 17:35:21 +0200, Ludwig Hügelschäfer wrote: > On 06.07.17 15:12, Lancon Erocan wrote: >> I know there is indeed security issue on auto-filling, but there is no >> reason to disallowing pasting. In that case I have no mean to input a >> /*REALLY */secure password generated from my

[Enigmail] U+2705 HEAVY WHITE CHECK MARK (for key import)

hey enigmail folks-- i see the use of unicode code point U+2705 (HEAVY WHITE CHECK MARK) in importInfoSuccess as broken with some font sets. here's a view of the import key dialog box on Debian with the standard set of fonts involved: i suspect there's a general expectation that this should be

[Enigmail] testing enigmail

hey all-- as far as i can see, enigmail's test suite is all unit tests. are there any full-stack, UI-level tests that would make sense to run? I was thinking of writing some sort of tests for the debian continuous integration infrastructure (https://ci.debian.net/) that would exercise the whole

Re: [Enigmail] gpg-connect-agent invocations

On Tue 2017-06-06 08:17:23 +0200, Patrick Brunschwig wrote: > On 05.06.17 17:20, Daniel Kahn Gillmor wrote: >> i notice that in e68dfc8260ebf976ba50845e794c9fac0d262975 enigmail is >> now invoking gpg-connect-agent, and then sending it commands on stdin. >> >> i

Re: [Enigmail] secret keys missing trust error

Hi Christian-- Thanks for the report. i'm filling in this mail with images in-line for future readers (after imgur removes the images) and a textual representation for the visually-impaired, and for indexers (to make it easier to search if a similar issue arises). A few diagnostic questions are

Re: [Enigmail] [ANN] Enigmail v1.9.7 available

On Sat 2017-05-13 18:50:23 +0200, Patrick Brunschwig wrote: > I'm happy to announce the availability of Enigmail v1.9.7 for > Thunderbird versions 45 and 52, and SeaMonkey 2.35 and newer. thanks! I've uploaded this to debian unstable. Unless there are objections here, i'm inclined to ask the

[Enigmail] [PATCH] Allow re-certifying keys that have expired certifications.

Some people have made expiring certifications on other keys. After such a certification expires, they might want to re-certify with the same key (e.g. if they've checked with the other person that they're still using the key). If this happens, enigmail fails obscurely ("signing failed"). In the

[Enigmail] [mogliii] Documentation about --list-secret-keys output

The attached thread came through on gnupg-users, but the most recent question in it (the interaction between enigmail and smartcards) might be more relevant over here on the enigmail mailing list. Any ideas about how to sync up enigmail's UI and smartcards? Regards, --dkg --- Begin 

Re: [Enigmail] Permanently decrypt received emails

On Tue 2017-02-14 02:32:15 -0500, vv01f wrote: > On 14.02.2017 08:20, vv01f wrote: >> Is there any option to make it signed first intentionally in enigmail or >> gpg to ensure this is will happen? > > Well, it is the standard[0], is there any otion still to intentonally > change it? > > [0]:

Re: [Enigmail] Problem with new version of Enigmail

On Sat 2016-11-12 23:04:51 +0900, Patrick Brunschwig wrote: > I created a new build that reverts the change causing the issue. Please > download the following version of Enigmail: > https://www.enigmail.net/download/nightly/enigmail-nightly-1.9.6.1.xpi is this going to be an official release? if

Re: [Enigmail] Question: BCC makes the signature wrong?

On Mon 2016-11-07 11:40:56 -0600, Bernhard Kleine wrote: > I have sent a signed email to several people, some of them in BCC, since > we donot want to share email adresses. Now, in the sent order the mail > is shown with Enigmail seal: correct signature by Bernhard Kleine. > However in Incoming

Re: [Enigmail] [ANN] Enigmail v1.9.6 available

Hi Patrick-- On Sat 2016-11-05 12:35:14 -0400, Patrick Brunschwig wrote: > I'm happy to announce the availability of Enigmail v1.9.6 for > Thunderbird versions 38, 45 and newer, and SeaMonkey 2.35 and newer. Thanks for this release! I notice that there is no git tag on sourceforge: git

Re: [Enigmail] [ENIGMAIL-1.9-BRANCH PATCH] keep options distinct

On Sat 2016-10-29 10:49:23 -0400, Patrick Brunschwig wrote: > On 29.10.16 16:26, Daniel Kahn Gillmor wrote: >> On Sat 2016-10-29 05:09:12 -0400, Patrick Brunschwig wrote: >>> The problem is that there is no output on stderr, even though >>> --status-fd 2 is specified. I

Re: [Enigmail] [ENIGMAIL-1.9-BRANCH PATCH] keep options distinct

On Sat 2016-10-29 05:09:12 -0400, Patrick Brunschwig wrote: > The problem is that there is no output on stderr, even though > --status-fd 2 is specified. I added --no-verbose because "verbose" > options in gpg.conf make gpg ignore --status-fd 2. Apparently there is > something more in your

Re: [Enigmail] [ENIGMAIL-1.9-BRANCH PATCH] keep options distinct

On Fri 2016-10-28 12:57:34 -0400, Patrick Brunschwig wrote: > On 28.10.16 18:42, Daniel Kahn Gillmor wrote: >> On Fri 2016-10-28 12:10:34 -0400, Ludwig Hügelschäfer wrote: >> >>> Just tested: enigmail-1.9-branch imports a key from file as well as >>> master here.

Re: [Enigmail] [ENIGMAIL-1.9-BRANCH PATCH] keep options distinct

On Fri 2016-10-28 12:10:34 -0400, Ludwig Hügelschäfer wrote: > Just tested: enigmail-1.9-branch imports a key from file as well as > master here. What version of GnuPG were you using to test? I'm using 2.1.15-8 (on debian testing/unstable). --dkg

Re: [Enigmail] [ENIGMAIL-1.9-BRANCH PATCH] keep options distinct

On Thu 2016-10-27 12:13:56 -0400, Daniel Kahn Gillmor wrote: > args is a list of distinct options, not a comma-separated string. Even with this patch applied, i find that running enigmail-1.9-branch, i can't import a key from a file. Take as an example the attached file. From the key managem

[Enigmail] [ENIGMAIL-1.9-BRANCH PATCH] keep options distinct

args is a list of distinct options, not a comma-separated string. --- package/key.jsm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/key.jsm b/package/key.jsm index ecdbdae..ab4b739 100644 --- a/package/key.jsm +++ b/package/key.jsm @@ -195,7 +195,7 @@ var EnigmailKey

[Enigmail] clearsigned messages showing up blank

hey enigmail folks-- i'm running enigmail 1.9.5-2 on debian with icedove 1:45.4.0-1 I just received a message structured like this: A└┬╴multipart/signed 26760 bytes B ├┬╴multipart/mixed 1689 bytes C │└─╴text/plain 1115 bytes D └─╴application/pgp-signature attachment [signature.asc] 1188 bytes

Re: [Enigmail] Debian Jessie only offers Enigmail 1.8.2, is it safe to install 1.9.5 from Sid?

On Mon 2016-09-12 12:41:41 +0200, Vatta wrote: > Am 11.09.2016 um 17:50 schrieb Patrick Brunschwig: >> It depends on the Thunderbird version. If you are using Thunderbird 38, >> then you better stick with Enigmail 1.8.2. If you are using Thunderbird >> 45 or newer, you can upgrade to Enigmail

Re: [Enigmail] Mac pinentry Problem

On Wed 2016-09-07 20:47:59 +0200, Tom Ritter wrote: > When I choose an encrypted email in Thunderbird, it displays a blank > preview page, no prompt for passphrase. When I cache my password by > using gpg on the command line, then it decrypts. > > I am using pinentry-mac from homebrew and

Re: [Enigmail] Mac pinentry Problem

On Wed 2016-09-07 20:47:59 +0200, Tom Ritter wrote: > Strangely, all the items I replaced with etc are not in my > keyring. Checked by doing gpg --fingerprint --fingerprint --list-keys > | grep (with the first 4 octets of each key). are you sure about that? pinentry refers to a key by

[Enigmail] [PATCH] use modern keyservers as examples

default to using the keyserver pool as an example, rather than encouraging the use of proprietary or defunct keyservers. --- lang/bg/enigmail.dtd | 2 +- lang/ca/enigmail.dtd | 2 +- lang/cs/enigmail.dtd | 2 +- lang/el/enigmail.dtd | 2 +- lang/es-AR/enigmail.dtd

Re: [Enigmail] Have to killall and relaunch gpg-agent after every reboot..

On Thu 2016-09-01 16:28:44 -0400, Bitcoin Admin wrote: > Yes, that 'other user' was me. And a fresh gnupg install solved the > dilemma, just imported the keyring and trustdb if you could send me a diff between your old gpg.conf and gpg-agent.conf (the ones that don't work) and the new ones (that

Re: [Enigmail] Problems with sorting messages encrypted with Memory Hole standard

On Tue 2016-08-09 02:11:47 -0400, Patrick Brunschwig wrote: > The implementation in the next major version of Enigmail will no longer > encrypt the "References" header automatically (you can still enable it > in a preference). I know this leaks more data than ultimately desired, > but it's still

Re: [Enigmail] [ANN] Enigmail v1.9.4 available

Hi Patrick-- On Mon 2016-07-04 12:05:13 -0400, Patrick Brunschwig wrote: > I'm happy to announce the availability of Enigmail v1.9.4 for > Thunderbird versions 38, 45 and newer, and SeaMonkey 2.35 and newer. I'd already incorporated most of these fixes into debian's 1.9.3-2, but i've just

Re: [Enigmail] Unverified signatures and mailing lists

Hi Duncan-- On Wed 2016-06-22 19:39:51 -0400, Duncan Guthrie wrote: > When I send messages to mailing lists, they have started to become > 'unverified'. When I send the email and sign it, in my 'sent' folder > the signature is good. However, when the mailing list receives it, the > signature is

Re: [Enigmail] Strange error msg

[ Please send a new e-mail when a new question, rather than replying to an existing e-mail and "hijacking" a previous thread. ] On Wed 2016-06-01 17:06:14 -0400, David Vallier wrote: > Today enigmail/gpg told me that a persons key wasn't compatible with my > version of gpg (using gpg2) what

Re: [Enigmail] Rules for attaching public key

On Wed 2016-06-01 16:28:51 -0400, Ludwig Hügelschäfer wrote: > On 01.06.16 19:52, Daniel Kahn Gillmor wrote: > >> I agree that keeping some state (or being able to infer state) about >> whether your peer likely has your key would be a useful thing. I'm not >> sure wh

Re: [Enigmail] Rules for attaching public key

On Wed 2016-06-01 13:46:28 -0400, Bob Henson wrote: > On 01/06/2016 6:32 pm, Hakuch wrote: >> are there any possibilities to create rules for public key attaching? >> Currently, I send always my public key to everyone, even if I sent it >> already 2000 times to a specific person. > > Why not just

Re: [Enigmail] Enigmail Message Filters: Decrypt only

On Sat 2016-03-26 20:31:45 -0400, Robert J. Hansen wrote: > The complete list of must-haves: [ ... ] > This list of copy-if-exists works for GnuPG 1.4, 2.0, and 2.1. Or, copy everything and then delete random_seed before trying to use GnuPG :) --dkg

Re: [Enigmail] Importing Sec keys to Enigmail

Hi Tiger-- On Fri 2016-03-11 19:17:25 -0500, tiger.rail...@nili.ca wrote: > Have exported secret keys from APG on Android and attempted to import to > Enigmail on Thunderbird. Though it seems like nothing was imported. People on this list want to be helpful, but you haven't provided enough

Re: [Enigmail] [BUG] Character encoding mix-up when encrypting Inline.

On Wed 2016-03-02 04:27:28 -0500, Lachezar Dobrev wrote: > My outgoing e-mail is set to send in UTF-8. > The 'use default encoding' option has a common negative effect: there are > numerous encodings that support Cyrillic, and not all mail agents (quite a > few web-mail agents) support MBCS

Re: [Enigmail] Using PGP-MIME vs inline PGP?

Hi there-- On Wed 2016-02-24 17:37:32 -0500, Datse Multimedia Information wrote: > When I opened Thunderbird today I received a message about the use of > PGP-MIME as the new "default setting". The "old" recommednation was > that inline PGP (at least for signed messages, though not nescesarily >

  1   2   3   >