On Fri, 27 Mar 2015 17:07, j...@jcea.es said:
> My problem is that any change to the pubring, like downloading a new
> key, refreshing, adding a new local signature with "--lsign", etc., will
> force a trustdb update (in the next execution. For instance, decrypting
A new key signature may chnage
On 27-03-2015 14:21, Martin Behrendt wrote:
> So especially when introducing new algorithms which might be tampered
> with, using e.g. an old style RSA Key as one layer and ECC as a second
> should help against this. Or am I missing something here?
Why would you want to use a suspect algorithm if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Thursday 26 March 2015 at 11:57:43 PM, in
, Mike Ingle wrote:
> That's more or less what it does. When you get an email
> from j...@somewhere.com, it fetches that key id and
> adds it to your keyring. If you get an email from a
> differen
On 28/03/15 15:59, MFPA wrote:
> Using "darknet" services to enhance privacy does not equate to
> "dodgy".
No, but nobody said the adjective was used tautological.
It's like someone says "they're doing shady business in a dark alley"
and you protest "Hey, I know plenty proper businesses that are
On 3/28/15 3:48 AM, Werner Koch wrote:
Sorry for this. It has already been fixed in the repo,
Just out of curiosity, do you have an ETA on a new release?
--
I am conducting an experiment in the efficacy of PGP/MIME signatures.
This message should be signed. If it is not, or the signature doe
Hi,
Notice that Iceland mirror are not working:
ftp://ftp.hi.is/pub/mirrors/gnupg/
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Am 27.03.2015 um 14:21 schrieb Martin Behrendt:
> On 26.03.2015 18:40, Pete Stephenson wrote:
>>
>> People have raised concerns about the NIST curves, but they are part
>> of the RFC 6637 standard so compliant programs must implement P-256,
>> may implement P-384, and should implement P-521.
>>
>>
