Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spec: Replace .cosign with .sig in the suffix #249

Closed
dlorenc opened this issue Apr 13, 2021 · 4 comments · Fixed by #287
Closed

Spec: Replace .cosign with .sig in the suffix #249

dlorenc opened this issue Apr 13, 2021 · 4 comments · Fixed by #287
Milestone

Comments

@dlorenc
Copy link
Member

dlorenc commented Apr 13, 2021

See #214

We should do this before 0.3, maybe support both for a release then go back to just one for 0.4

@dlorenc dlorenc added this to the 0.3.0 milestone Apr 13, 2021
@dlorenc
Copy link
Member Author

dlorenc commented Apr 14, 2021

I don't think we'll get to this in 0.3, but when we do it we should try to bump the version pinned here: https://github.com/sse-secure-systems/connaisseur/blob/feat/cosign/docker/Dockerfile#L15

@dlorenc
Copy link
Member Author

dlorenc commented Apr 15, 2021

Maybe we can support an env var for a release or two called "COSIGN_SUFFIX" to help out here instead of double writing.

@dlorenc
Copy link
Member Author

dlorenc commented Apr 18, 2021

Dual writing is probably the easiest thing for 0.3, it's not really a dual write, but a dual tag. triangulate can return just one though.

@dlorenc dlorenc mentioned this issue Apr 20, 2021
5 tasks
@dekkagaijin
Copy link
Member

Here's the 2 sanest options I can think of:

  1. Rip off the band-aid; new clients sign to and verify from the new location only.
  2. Write to and verify from both tags for a time (1 release?). This allows for new clients to see signatures from old clients and vice versa.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants