automate trusted keys management #4

Closed
opened 2 years ago by x1ddos · 1 comments
x1ddos commented 2 years ago
Owner

at the moment, changes are verified with git pull --verify-signatures in https://git.qcode.ch/nakamochi/sysupdates/src/commit/e856de67/update.sh#L40 which runs gpg-verify.

but the keys which sign commits must first be marked as trusted in the gpg keychain.

at the moment, changes are verified with `git pull --verify-signatures` in https://git.qcode.ch/nakamochi/sysupdates/src/commit/e856de67/update.sh#L40 which runs gpg-verify. but the keys which sign commits must first be marked as trusted in the gpg keychain.
x1ddos added this to the MVP project 2 years ago
Poster
Owner
moved to https://github.com/nakamochi/sysupdates/issues/4
x1ddos closed this issue 7 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
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: nakamochi/sysupdates#4
Loading…
There is no content yet.