Problems with key available in v1.4.19 but not v2.1.5

[Ludwig Hügelschäfer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 18.07.15 16:11, Philip Neukom wrote:
> On 17.07.2015 19:36, Robert J. Hansen wrote:
>> 
>> I'd suggest generating a new certificate -- after 20 years you're
>> due for one.  :)
>> 
> 
> Thank you, Robert.  I'll revoke the old one and create a new.
> 
> I'll need to do some reading of the docs but just curious if there
> is there a way to move the trust rating from the old cert to the
> newly created one other than ask those who signed to resign?

You can sign the new cert with your old one, but I'm not sure if that
trust chain holds if you revoke your old cert. Also, more and more
people will not be able to hold your old cert in their keyring when
they migrate to use gpg2 modern (2.1.x).

Ludwig

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJVqmz8AAoJEDrb+m0Aoeb+uBYP/00BK6CZ7sjZ8wb/K5EuntRw
50xeM1QD5a9n4CiPmOCtOF7ty4SVK36FBygNutGOQYiY6nzf5x8mlfgaHO0kdFrR
+O2KcHBGlTTYpZF5u797cNAu8UVSBqsrUxAJcn/02kpvmNay+/TikOFI7EMRH9D1
gwEkqzt6hVrsT7dYNYugnY5A8zRu1Qdhixm7dWdaAaCUvqoJqtnCpnRZvasZToTF
ka5NuzabVI1/gM2jPBFA3a/C41WlGlea5SnZKhYxVgNdn7DXBes0rQx0IYurumdo
Hw+1qhXmWzaJIOW+/ojhklvpexsh75t44Rtjj8yCxR6HR+78JjJAqCGlUf77yGT4
dw/FE+RvwpQFvrjm2/erpqt4qRSlbYsYYGn1y6EkS4jQKmpvkBjHOuf3vIwEYe9a
fGqJ8LJVo24JzLKJs+xsBLYDHNb2cunK/EV66IPiN+1YAB/9Hz/PybxT7mxKLT+/
MViYpHle9/bCwXxPLKB6qa4MqSsS4GniCsaxZ95/7ZAUNhITSGPfdkU575mXWGmt
4LRmRo/oXXCdlkYJR1U25FLA8KnfcRYOyqfA716kvCpcwvR/sbtd40aXsddsAp1N
Y+MRhhklYs5PlgE7ho4FsvuXNtZi2bo7thCV7dE/1MmRP22XVkdF6qZ492okvIuP
PnlJ1PkcoW1AcqoI6uj5
=ImLA
-----END PGP SIGNATURE-----