mirror of
https://github.com/NixOS/rfcs.git
synced 2025-12-14 21:11:14 +01:00
0149-cache-key-rotation: add some alternatives
This commit is contained in:
parent
7681874854
commit
407a35e6e9
1 changed files with 7 additions and 1 deletions
|
|
@ -58,7 +58,13 @@ Why should we *not* do this?
|
|||
# Alternatives
|
||||
[alternatives]: #alternatives
|
||||
|
||||
What other designs have been considered? What is the impact of not doing this?
|
||||
- change nothing, obviously
|
||||
- also resign old `*.narinfo`. Maybe it's not too hard.
|
||||
It would help people wanting ot use old builds.
|
||||
- double-sign `*.narinfo` for some time. (also not an exclusive alternative)
|
||||
I don't know if consumers support multiple signatures.
|
||||
It doesn't seem to give us significant advantage though;
|
||||
acceptance of multiple keys seems more advantageous.
|
||||
|
||||
# Unresolved questions
|
||||
[unresolved]: #unresolved-questions
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue