-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 01.01.2015 um 18:10 schrieb Linux Debian:
(...)
> I've updated my GnuPG key and send to keyservers. What I updated ?
> I've just deleted 2 expired subkeys and added one with a longer
> (in 2015) expiration. But (...) those 2 expired subkeys stil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Peter,
I just wanted to say thank you very much for the explanation. It was very
enlightening.
I especially like the fact that, despite nobody asking specifically about
SHA-1, you
still decided to take the time to write a lengthy message explainin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
David,
it is not a gpg2 problem and it is also not relatd to modern versions
of your mail programmes. In my case Thunderbird 31.2 with
Enigmail 1.7 runs just fine with GnuPG 1.4.16. I also have GnuPG
2.0.22 installed as gpg2, but I'm not actively us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear David,
On 14. November 2014 18:30:19 MEZ, "da...@gbenet.com" wrote:
>On 14/11/14 13:38, Gabriel Niebler wrote:
>> (...)
>> (...) maybe you can walk
>> us through exactly what you did and we'll see if we can
a passphrase to unlock the secret key for
user: "Gabriel Niebler "
2048-bit RSA key, ID 0x65A3F1CC8303C0EC, created 2014-03-16
(subkey on main key ID 0xD05AF6C786CB34F4)
gpg: encrypted with 2048-bit RSA key, ID 0x65A3F1CC8303C0EC, created
2014-03-16
"Gabriel Niebler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm sorry, I know this is OT for the list, but...
Am 21.08.2014 um 15:54 schrieb Robert J. Hansen:
>> GNU community members and collaborators have discovered
>> threatening details about a five-country government surveillance
>> program codenamed HA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 24.06.2014 09:36, schrieb Cpp:
> I was going to create a new PGP key myself by following that
> article. Werner, do you have any more input or comments to add
> regarding that article? I am curious to hear input from multiple
> sources/people.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>> A key on my keyring is "valid" if it is not expired or revoked.
>> It is "authentic" if it bears one signature from one of my keys,
>> or several signatures from other keys to which I have granted
>> marginal authority to authenticate keys. """
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 25.04.2014 00:22, schrieb Doug Barton:
> Isn't what you're talking about "verification?"
To my mind, "verification" is the _process_ whereby the _properties_
like "validity" and "authenticity" are established*. I see a
difference there, but one c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Peter Lebbing has thankfully pointed out that, out of my two
suggestions, "authenticity" is the word that should be preferred.
I agree with him on this, so I shall use that word here.
> A key on my keyring is "valid" if it is not expired or revoked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 24.04.2014 11:13, schrieb Peter Lebbing:
> I think "authenticity" covers the overtones much better than
> "validity", now that you mention it. It even makes me wonder why it
> wasn't chosen in the first place :). You have convinced me that it
> is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tl;dr: "validity" is confusing, please consider using "ownership" or
"authenticity" for same concept.
Dear all,
it seems to me that the problem here is mainly one of semantics. The
technical concepts are clear to everyone involved, the question is how
12 matches
Mail list logo
