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

Detach-sign all release files #588

Closed
ghost opened this issue Jan 5, 2017 · 4 comments
Closed

Detach-sign all release files #588

ghost opened this issue Jan 5, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Jan 5, 2017

Related: #586

It'd be incredibly helpful for automated builds and distros that don't have their own packages with files attached (Gentoo/Arch's AUR/NixOS) if all files in a release could be detach-signed with GPG by a key with a common trustee.

Could also make the packaging flow much nicer/less prone to not checking signatures and hashes for other distros and users in general.

@rvagg
Copy link
Member

rvagg commented Jan 5, 2017

Are you talking about detached signature files here or key trust? Or somehow both?

We've been making detached signatures since nodejs/node#9071, although we haven't updated the docs to demonstrate how to use this as we've been waiting for all release lines to be updated with the new sig style, tracking in nodejs/node#6821. Since it's been in place for a while now we should probably go ahead and update the docs to tell how to verify with the detached signatures instead of the inline signatures.

@rvagg
Copy link
Member

rvagg commented Jan 5, 2017

... catching up on IRC ... are you perhaps talking about detached signatures for each file in the releases? So ~ double the number of files in the release directories than we have now, an .asc for each one?

@ghost
Copy link
Author

ghost commented Jan 5, 2017

It's somehow both I guess. I just noticed that the releases are done by different people and signed with the personal keys - if there's a release signing key that trusts those personal keys, that's great.

A small set of keys to expect would work too, decentralizes the trust a little better Arch does it.

it's mostly that it can be a little hard to automate the checks if files are not signed individually. If I had a node-v.tar.xz.sig I could automate the packaging entirely.

So yes, double the number of files (-2 because don't resign the shasums, obviously), seems to be quite common actually - if that's too much clutter, well, shame.

@Trott
Copy link
Member

Trott commented Mar 22, 2019

Closing due to long period of inactivity. Feel free to re-open if this is a thing. I'm just trying to close stuff that has been ignored for sufficiently long that it seems likely it's not something we're going to get to.

@Trott Trott closed this as completed Mar 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants