On Thu, 29 Dec 2016 12:37:03 +, MFPA
<2014-667rhzu3dc-lists-gro...@riseup.net> wrote:
>On Sunday 27 November 2016 at 5:15:55 PM, in
>, Carola
>Grunwald wrote:-
>
>
>> But no, unfortunately it's a Windows server
>> application with GnuPG, Tor,
>> Mixmaster and Hamster embedded. And in a server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sunday 27 November 2016 at 5:15:55 PM, in
, Carola
Grunwald wrote:-
> But no, unfortunately it's a Windows server
> application with GnuPG, Tor,
> Mixmaster and Hamster embedded. And in a server
> environment it's
> problematic to switch syste
Werner Koch wrote:
>On Wed, 23 Nov 2016 03:28, c...@nymph.paranoici.org said:
>
>> Sure, I like v1.4's small footprint and its reliability. But as the
>> --faked-system-time option, important in my application for privacy
>> reasons, wasn't backported to v1.4, I had to migrate to v2.1. I'm still
On Wed, 23 Nov 2016 03:28, c...@nymph.paranoici.org said:
> Sure, I like v1.4's small footprint and its reliability. But as the
> --faked-system-time option, important in my application for privacy
> reasons, wasn't backported to v1.4, I had to migrate to v2.1. I'm still
If you are running on a g
Daniel Kahn Gillmor wrote:
>On Wed 2016-11-23 03:46:57 -0500, Carola Grunwald wrote:
>> With GnuPG 1.4 I had no agent. And, in case it is, I've no idea why with
>> 2.x such a passphrase cache with all its risks has to be mandatory.
>
>in 2.0, the agent is a passphrase cache. in 2.1, the agent is
On Wed 2016-11-23 03:46:57 -0500, Carola Grunwald wrote:
> With GnuPG 1.4 I had no agent. And, in case it is, I've no idea why with
> 2.x such a passphrase cache with all its risks has to be mandatory.
in 2.0, the agent is a passphrase cache. in 2.1, the agent is a proper
cryptographic agent, whi
Daniel Kahn Gillmor wrote:
>On Tue 2016-11-22 11:20:26 -0500, Carola Grunwald wrote:
>> They don't have direct access to any key. Nevertheless by using someone
>> else's cached passphrase with 2.1 and its all-embracing keyring they may
>> succeed in decoding data not meant for them.
>
>fwiw, the
Peter Lebbing wrote:
>On 22/11/16 17:20, Carola Grunwald wrote:
>> They don't have any system account at all. These are users of a
>> messaging system, only allowed to access its POP3, SMTP and NNTP
>> service.
>
>Perhaps 1.4 is the best release for you... you'll miss out on Elliptic
>Curve, but
On Tue 2016-11-22 11:20:26 -0500, Carola Grunwald wrote:
> They don't have direct access to any key. Nevertheless by using someone
> else's cached passphrase with 2.1 and its all-embracing keyring they may
> succeed in decoding data not meant for them.
fwiw, the same concerns hold for a shared gpg
On 22/11/16 17:20, Carola Grunwald wrote:
> They don't have any system account at all. These are users of a
> messaging system, only allowed to access its POP3, SMTP and NNTP
> service.
Perhaps 1.4 is the best release for you... you'll miss out on Elliptic
Curve, but other than that, it's still a
Peter Lebbing wrote:
>On 21/11/16 15:20, Carola Grunwald wrote:
>> As for each single decryption task only a defined passphrase is
>> allowed to be used it's essential to have caching, which implicates
>> the risk of unauthorized passphrase usage, strictly deactivated.
>
>Why do you lump these us
On 21/11/16 15:20, Carola Grunwald wrote:
> As for each single decryption task only a defined passphrase is
> allowed to be used it's essential to have caching, which implicates
> the risk of unauthorized passphrase usage, strictly deactivated.
Why do you lump these users together? At a first glan
Hello Werner,
thanks for your fast reply.
On Mon, 21 Nov 2016 10:30:51 +0100, you wrote:
>On Sun, 20 Nov 2016 22:18, c...@nymph.paranoici.org said:
>
>> to gpg-agent.conf the official way to deactivate passphrase caching
>> completely and make GnuPG only use the term transferred with the
>
>Plea
On Sun, 20 Nov 2016 22:18, c...@nymph.paranoici.org said:
> to gpg-agent.conf the official way to deactivate passphrase caching
> completely and make GnuPG only use the term transferred with the
Please describe what you want to achieve.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Aus
Hi,
is adding
| default-cache-ttl 0
and/or
| max-cache-ttl 0
to gpg-agent.conf the official way to deactivate passphrase caching
completely and make GnuPG only use the term transferred with the
--passphrase option?
Thanks
Caro
___
Gnupg-users mail
Hi,
is adding
| default-cache-ttl 0
and/or
| max-cache-ttl 0
to gpg-agent.conf the official way to deactivate passphrase caching
completely and make GnuPG only use the term transferred with the
--passphrase option?
Thanks
Caro
___
Gnupg-users mail
16 matches
Mail list logo
