GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||
GeezerVison is showing github.com — Inadvertent disclosure by mhdawson · Pull Request #36155 · nodejs/node Conversation
Member
Checklist
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
|
Review requested:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Are the n-api changes here intentional? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Link to the repository? Or should we keep it without a link on purpose?
Also, I assume it will be a repo on nodejs-private?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I've not created the repo yet, but a link makes sense. It should only be accessible to those who have access to private repos within the org
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
@mmarchini added the link in the first reference, not sure if we need to make all references a link or not.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Also, I assume it will be a repo on nodejs-private?
No, its a private repo in the nodejs org as I don't believe we can move issues across organizations.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I see. The downside is that folks who have access to private repos in this org but not on the repo we usually use for security releases will have access to the issue. It's probably fine though, it only means some folks in moderation and CommComm will have access to the issue even when they don't have access to security release discussions (which is still better than keeping the issue public).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Add process for handling premature disclosure of a security vulnerability in the public repos. Signed-off-by: Michael Dawson <[email protected]>
06b7d65 to
83c1c12
Compare
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Co-authored-by: Richard Lau <[email protected]>
Co-authored-by: Richard Lau <[email protected]>
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
lgtm. I think we need to open a request on nodejs/admin to create the repository, correct?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: mary marchini <[email protected]>
|
@mmarchini good call on creating the request in admin. Here is the list: nodejs/admin#573 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Add process for handling premature disclosure of a security vulnerability in the public repos. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #36155 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Mary Marchini <[email protected]> Reviewed-By: Rich Trott <[email protected]>
|
Landed as 9cf2341 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Add process for handling premature disclosure of a security vulnerability in the public repos. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #36155 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Mary Marchini <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Add process for handling premature disclosure of a security vulnerability in the public repos. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #36155 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Mary Marchini <[email protected]> Reviewed-By: Rich Trott <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.