On 03/28/2015 08:30 PM, Daniel Kahn Gillmor wrote:
> [so much for following up on gpg-devel; i'm replying to enigmail because
> that's where this message went, even though i don't understand the
> reason to keep this non-enigmail discussion here]
>
> On Sat 2015-03-28 15:09:15 -0400, Doug Barton wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Mike,
I think that INLINE/MIME, signed/unsigned and blank subject should not depend
on each other. That is, having one set or not should not yield other results for
another. Users would not expect this (and rather manually set it).
> We would no
On 3/26/15 12:36 AM, Patrick Brunschwig wrote:
Automatic key-retrieval is a GnuPG function; I'd expect you don't see
the message if the key could be found by GnuPG.
Hmmm, Ok. I was able to eventually retrieve the key, so I had assumed
that Enigmail's behavior had changed in this regard. It co
On 3/28/15 12:30 PM, Daniel Kahn Gillmor wrote:
[so much for following up on gpg-devel; i'm replying to enigmail because
that's where this message went, even though i don't understand the
reason to keep this non-enigmail discussion here]
On Sat 2015-03-28 15:09:15 -0400, Doug Barton wrote:
Fina
[so much for following up on gpg-devel; i'm replying to enigmail because
that's where this message went, even though i don't understand the
reason to keep this non-enigmail discussion here]
On Sat 2015-03-28 15:09:15 -0400, Doug Barton wrote:
> Finally, someone else already posted the right answer
On 3/28/15 11:57 AM, Daniel Kahn Gillmor wrote:
If the only concern is leaving sensitive data in the clipboard after
use, maybe pinentry could*accept* pastes, but then also clear the
clipboard after it was pasted into?
First, this discussion is moot because Werner won't change this.
Second, w
Olav,--
Thank you for your very thoughtful reply. The point of issue that
prompted me to write arose when I attempted to sign a message I had
written regarding blank subject lines. As soon as I attempted to sign
the message I was warned that my message was being converted to plain
text,-- which
[redirecting to gnupg-devel, setting mail-followup-to: there]
On Wed 2015-03-25 18:26:38 -0400, Robert J. Hansen wrote:
>> My guess is that this is for added security.
>
> Correct. Werner Koch has said several times that he will not change the
> code to permit C&P into the dialog box, as that wou
On 3/28/15 6:31 AM, Mike Acker wrote:
On 03/28/2015 07:21 AM, Ron OHara wrote:
Hi,
In Thunderbird, you are warned if you send an email with a blank
Subject.If the message is to be encrypted, best practice is to NOT
have a Subject line. The Subject line is not encrypted and thus 'leaks'
inf
When starting a new topic please don't reply to a message on the list
and change the subject line. Doing so causes your new topic to show
"under" the previous one for those using mail readers that thread
properly, and may cause your message to be missed altogether if someone
has blocked that th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Mike,
> there should be 3 selections: Encryption, Signing, and PGP/MIME
I disagree. Aunt Sally will ONLY care about encrypt or not. More learned folks
may want to change their default signing setting for specific messages. But only
nerds care to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28.03.15 15:59, Blaise Pascal wrote:
> Hi,
>
> using Linux Mint 17 / Thunderbird (24.4.0) / Enigmail 17.2 with
> gpg2... Once deciphered, Enigmail (or gpg-agent) keeps the
> passphrase forever in memory although I have a
> .gnupg/gpg-agent.conf c
Hi,
using Linux Mint 17 / Thunderbird (24.4.0) / Enigmail 17.2 with gpg2...
Once deciphered, Enigmail (or gpg-agent) keeps the passphrase forever in
memory although I have a .gnupg/gpg-agent.conf containing:
max-cache-ttl 15
default-cache-ttl 15
I'm not sure that gpg-agent.conf is correctly read
I see they revised the Enigmail Toolbar. are they taking lessons from
Julie Larson-Green ;) ?
anyway, there should be 3 selections: Encryption, Signing, and
PGP/MIME.Generally if you are just signing a message or actually
encrypting and signing -- you want to use PGP/MIME. I would then put
On 03/28/2015 07:21 AM, Ron OHara wrote:
> Hi,
>
> In Thunderbird, you are warned if you send an email with a blank
> Subject.If the message is to be encrypted, best practice is to NOT
> have a Subject line. The Subject line is not encrypted and thus 'leaks'
> information.
>
> Any ideas on how
Hi,
In Thunderbird, you are warned if you send an email with a blank
Subject.If the message is to be encrypted, best practice is to NOT
have a Subject line. The Subject line is not encrypted and thus 'leaks'
information.
Any ideas on how to:
1 - suppress the Thunderbird warning if Subject is
16 matches
Mail list logo
