You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shortly after, release v1.4.3 seems to have changed the key again, though I don't think it was announced. Note that the previous key was set to expire in 2023, but v1.4.3 was released on 2022, just a bit over a month after v1.4.1.
Additionally, I think it would be nice if the previous keys were documented for historical transparency. For example, why was "v2" added? Did the original key get compromised? Why was "v2" replaced so quickly, and without announcement? Why does the user ID of the current key refer to one developer (Joe Clapis <[email protected]>) as opposed to Rocket Pool (Smartnode Installation Signing Key v2) <[email protected]> and Rocket Pool (Smartnode Signing Key) <[email protected]> in the previous keys (2)?
(1): I believe the key was first published with v1.0.0 prerelease 4. Prerelease 3 published signatures but I don't think it included the signing key. I don't believe any prior releases were signed.
(2): Having lurked on the discord for a while, I recognize Joe Clapis (pretty sure he's personally answered my questions before 😅 ) and I trust the key. However, I still think it would be better practice to have an "official reference" for the active (and past) PGP keys.
The text was updated successfully, but these errors were encountered:
Release v1.0.0 includes a PGP key (1):
Release v1.4.1 notes that the signing key has been changed:
Shortly after, release v1.4.3 seems to have changed the key again, though I don't think it was announced. Note that the previous key was set to expire in 2023, but v1.4.3 was released on 2022, just a bit over a month after v1.4.1.
This "v3" key is the most recent key as far as I can tell; it has been used up until and including the most recent release (v1.10.0).
I think it would be helpful to document the current signing key somewhere on the website or git repository. For example, Geth lists their PGP keys on the download page of their website, and Lighthouse lists their PGP key in the README of their repository.
Additionally, I think it would be nice if the previous keys were documented for historical transparency. For example, why was "v2" added? Did the original key get compromised? Why was "v2" replaced so quickly, and without announcement? Why does the user ID of the current key refer to one developer (
Joe Clapis <[email protected]>
) as opposed toRocket Pool (Smartnode Installation Signing Key v2) <[email protected]>
andRocket Pool (Smartnode Signing Key) <[email protected]>
in the previous keys (2)?(1): I believe the key was first published with v1.0.0 prerelease 4. Prerelease 3 published signatures but I don't think it included the signing key. I don't believe any prior releases were signed.
(2): Having lurked on the discord for a while, I recognize Joe Clapis (pretty sure he's personally answered my questions before 😅 ) and I trust the key. However, I still think it would be better practice to have an "official reference" for the active (and past) PGP keys.
The text was updated successfully, but these errors were encountered: