Release signature verification #33

Open
opened 2026-08-24 23:03:32 +00:00 by zaprit · 0 comments
Owner

to reduce the risk of MITM attacks or malicious updates being distributed should the update server get compromised there should be a release signing key used.

to reduce the risk of MITM attacks or malicious updates being distributed should the update server get compromised there should be a release signing key used.
zaprit added this to the 2.0 milestone 2026-08-24 23:03:32 +00:00
zaprit added this to the 2.0 project 2026-08-24 23:03:33 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
HugeSpaceship/patchwork#33
No description provided.