-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: add GPG fingerprint for Fishrock123 #1324
Conversation
Awesome :) Good luck with releases. |
Also, my GPG keyprint is publicly verifiable here: https://keybase.io/fishrock |
Did you upload your public key to sks-keyservers.net? It doesn't appear to be visible yet. At least, I can't find it. |
@bnoordhuis went to upload.. chrome gives me a security error due to this: I mean it's just the pubkey, but still. |
Ah, it's using a certificate that's signed by a self-signed CA... why are we recommending sks-keyservers.net again? |
Well, again, my key and info is publicly verifiable and searchable on keybase. It looks like a lot of node-related people are on there too. |
Yeah, no reason to let that hold up this PR. LGTM. |
the https error is because that hostname resolves to a pool of hosts which identify as their own hostname. We are recommending sks-keyservers because it's a reliable way to get the key into the biggest GPG key pool, there are other hosts you can submit to and they'll end up in the same place I think but this is as good as any, minus the https problem |
addendum: the key has to be in that key pool before we can push forward with this, there are a number of automated download/install scripts out there, including https://github.com/iojs/docker-iojs/blob/6355158c25e37cce11847466eb11aee198540bed/1.6/Dockerfile#L4 that rely on this to work, keybase isn't helpful here |
I uploaded this to the keyserver, but can't find it in the search; can someone verify?
|
not yet, is that the same one you have the fingerprint for on this PR? |
ah, wait, sorry:
|
lgtm! let's do this! |
https://github.com/iojs/io.js/blob/v1.x/tools/release.sh#L53 Ah looks like it just searches it. |
PR-URL: nodejs#1324 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs#1324 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
8e65f00
to
8c6c376
Compare
you should be able to run that command on this branch and it won't bork now, if it works then merge this and get a release out! |
PR-URL: nodejs#48 Related: nodejs/node#1324 Related: nodejs/node#1225 Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@turistforeningen.no>
See #1225
Also includes better formatting for gpg key fingerprints in the readme.
R=@rvagg