On Tue 2015-07-21 23:36:45 +0200, ved...@nym.hush.com wrote:
> There could be a workaround, where the key is uploaded to the keyservers,
> but functionally unusable except to individuals whom the key-creator wants to
> use it:
>
> [1] Encrypt part of the public key symmetrically, the same way that
Hi list,
I have a key for some years which did not have an expiration time. Now,
I finally want to change this and changed the expiration time (via
--edit-key then expire, save).
To test if everything is now working as it should, I exported the keys
(--export, --export-secret-keys), deleted the
On Tue, 21 Jul 2015 19:31, r...@sixdemonbag.org said:
> Right now, I wouldn't recommend ECC for production use. We're still
> getting the kinks worked out of it, and it isn't beyond the realm of
> possibility to think we might see significant changes by GnuPG 2.2.
Nope, you won't see changes her
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22.07.15 16:36, flapflap wrote:
> Should I be worried by the warning or is this normal behaviour?
You should set ultimate ownertrust on your own key after
(re-)importing. Then it will become valid again.
Ludwig
-BEGIN PGP SIGNATURE-
Ve
Ludwig Hügelschäfer:
> On 22.07.15 16:36, flapflap wrote:
>
>> Should I be worried by the warning or is this normal behaviour?
>
> You should set ultimate ownertrust on your own key after
> (re-)importing. Then it will become valid again.
My key still looked/looks valid, even without changing th
Hi
On Tuesday 21 July 2015 at 10:36:45 PM, in
, ved...@nym.hush.com
wrote:
> (* Unless* you misjudged someone to whom you sent the
> passphrase, and he turns maliciously on you, and
> uploads the decrypted form
It could easily be accidental rather than malicious.
--
Best regards
MFPA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wednesday 22 July 2015 at 3:48:15 PM, in
, Werner Koch wrote:
> Nope, you won't see changes here - at least not for the
> standard NIST or Brainpool curves.
Is the format for encryption keys using Curve 25519
finalised/implemented yet?
- -
