Updating public key problem
Gabriel Niebler
gabriel.niebler at gmail.com
Thu Jan 1 22:28:40 CET 2015
-----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 still
> appear (...)
Yes, key servers are purely cumulative.
Information cannot be deleted or made to disappear from them,
including revoked or expired (sub)keys.
This is by design, so that noone can e.g. remove someone else's
(sub)key(s), signatures, preferences etc. from the key server network.
> (...) and that's why, in my opinion, why the sending an encrypted
> message doesn't work by the free service like -
> https://encrypt.to/linuxdebian@zoho.com Before the expirationd
> date of those 2 keys, the encrypt.to service worked.
I don't know that service, but if that is the case, then I suggest you
take it up with the people who run the encrypt.to service. If it
cannot handle expired subkeys then they don't implement the OpenPGP
standard correctly.
Cheers
gabe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJUpbwIAAoJEO7XEikU4kSzr0gH/jWaRd2+8f/uv74iRjRkVdyK
w8/wNFC1kgnnpCknabtQWZsyIdtltSSuH3Eg8RxuGQWqLAcguJ/5rvPO1DxyW142
7kuUZhOFHWKKzH6oK8jqCnf/FGEu4TSg20Qzf3KGiOB+AKGYAMEfEHo5KjwZfxYi
WRwMRhLj/eLa9HNbUQvTPTpVlZFhy7ueXB0kt7mhXt5yasa9QQIEX1YlPgr/QTL+
R8uHC3GMBHzHzcj/YqzXCx/dPX8gsnfdodEMgSzPvuGsnj3YJ65kuCSdYYgUpoJ4
MKJp+rldUQAFb/zMDObSHCgTOej3hP+yNHoTPnGC4JFiW7RJUBYhL+NVWG9wcaM=
=5yoP
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list