Is this the same as #8547 ? Wasn't the conclusion to get people to use --refresh-keys

I think the old key is revoked

On Monday, September 5, 2016, Michael Ford [email protected] wrote:

Is this the same as #8547 #8547
? Wasn't the conclusion to get people to use --refresh-keys .

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#8662 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGGmv5xDkIVUvZojcXFHn74FMFApzhNVks5qm2flgaJpZM4J0hmS
.

Yes, the old key is revoked. So --refresh-keys is a good idea to get the revocation certificate, but not a replacement for updating the key this time.

ACK 46606af, verified that the key in this pull, 0xD5566241A0295FA9 is the same new key as I have on file for @btcdrak.

utACK 46606af