Rekey event for vault.forkos.org #258
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: afnix/infra#258
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At last Congress, we have initialized vault.forkos.org in a semi-serious key ceremony setup.
I remember @ktemkin @puck @jade @yu-re-ka @janik and me having key shares.
Now that ForkOS is heading to a new future and governance structure (namely: AFNix), the current setup is blocking the people who are working on it.
I am planning to perform an online rotation of the keys and redistribute key shares to @delroth @tom-hubrecht
And would offer to @yu-re-ka one standalone keyshare (like the non-board members of the time).
For the next $BIG_EVENT, if there's enough people, we can redo an IRL key rotation.