Repository navigation
Update contributors.yaml with key invalidation info - #954
Conversation
|
@pedro-hos What's happening to your keys? Are you losing your laptops? :) You can just prolong your keys, you don't have to invalidate them each time... |
|
@rhusar No, I had to format my laptop with IBM Fedora and didn't save the keys. :-( |
|
@pedro-hos Gotcha... third time the charm! :) |
|
A preview of this PR is available at https://pr-954-wildfly-org.surge.sh |
| - id: ed25519/C1F87ABA8942F3E5 | ||
| key: FFF4 950E CA97 7904 558F 67E4 C1F8 7ABA 8942 F3E5 | ||
| link: https://keyserver.ubuntu.com/pks/lookup?search=FFF4950ECA977904558F67E4C1F87ABA8942F3E5&fingerprint=on&op=index | ||
| fingerprint: 2813 8A84 851C AF4C 87AC D1AF 59C5 2295 03E1 CCCD |
There was a problem hiding this comment.
@pedro-hos ????
The fingerprint was copied from the old key. The new entry has: fingerprint: 2813 8A84 851C AF4C 87AC D1AF 59C5 2295 03E1 CCCD
That is the fingerprint of the key being invalidated. The page displays this fingerprint and users verify signatures against it, so it must be:
fingerprint: FFF4 950E CA97 7904 558F 67E4 C1F8 7ABA 8942 F3E5
There was a problem hiding this comment.
my bad! I've just fixed it
Added invalidation details for a contributor's key.
rhusar
left a comment
rhusar
left a comment
There was a problem hiding this comment.
LGTM now.
You should have used your new @ibm.com address, but... next time.
Added invalidation details for a contributor's key.