store signing keys for nodens #86
No reviewers
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Fachschaft/nixConfig#86
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "nerf/nixConfig:nodens-deploy"
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?
This adds signing keys to nodens that all the other machines trust, so nodens can sign builds and we can deploy from there directly.
This is a first step towards CI
store signing keys for nodensto WIP: store signing keys for nodensWIP: store signing keys for nodensto store signing keys for nodens@ -32,1 +32,4 @@
# additional trusted keys for substituters for every machine
# right now it is only nodens so nodens can build system configs
# and we can deploy them from nodens.
Please describe somewhere how this is used (probably in the
Readme.md
where we also described building locally).@ -33,0 +34,4 @@
# right now it is only nodens so nodens can build system configs
# and we can deploy them from nodens.
# For security reasons we might want to move this to the vm part, as
# someone who can get controll of nodens and get hold of the build process
controll -> control
@ -33,0 +36,4 @@
# For security reasons we might want to move this to the vm part, as
# someone who can get controll of nodens and get hold of the build process
# can gain control of the other machines. While this is very handy
# and a step towards CI, we might not want this for backups.
I think its fine for backups as well.
@ -33,0 +37,4 @@
# someone who can get controll of nodens and get hold of the build process
# can gain control of the other machines. While this is very handy
# and a step towards CI, we might not want this for backups.
# (This is a tradeof between security and convinience)
convinience -> convenience
5c09cb3cdc
to5a64d39621
5a64d39621
tod74be71aa1