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

Remove security e-mail addresses #2179

Merged
merged 5 commits into from
Apr 16, 2019

Conversation

reedloden
Copy link
Contributor

@reedloden reedloden commented Apr 11, 2019

The web interface is preferred for security (HTTP via TLS vs. possibly unencrypted e-mail),
and using the e-mail addresses requires that the web interface be used to finalize reports.

As such, just remove the security e-mail addresses entirely and only refer to the HackerOne
web interface.

Fixes: nodejs/security-wg#123

The web interface is preferred for security (HTTP via TLS vs. possibly unencrypted e-mail),
and using the e-mail addresses requires that the web interface be used to finalize reports.

As such, just remove the security e-mail addresses entirely and only refer to the HackerOne
web interface.
@reedloden reedloden added the content Issues/pr concerning content label Apr 11, 2019
@reedloden reedloden self-assigned this Apr 11, 2019
@ghost ghost self-requested a review April 11, 2019 03:10
@Trott
Copy link
Member

Trott commented Apr 11, 2019

@nodejs/security-wg

@reedloden
Copy link
Contributor Author

Remove email for the Chinese version
@e-jigsaw
Copy link
Contributor

Added ja version e-jigsaw@97a6332

@lirantal
Copy link
Member

lirantal commented Apr 12, 2019

While I would like to provide more alternatives for researchers to report issues, as it currently stands, even if you send an email you actually need to follow-up with a login to H1 to submit the report, which is why I agree with this PR clearly promoting the H1 program instead of the e-mail which may provide less than obvious user experience.

@sam-github
Copy link
Contributor

Seems reasonable to me, @nodejs/security , any objections?

@rvagg
Copy link
Member

rvagg commented Apr 16, 2019

I guess not given the current situation; although I'm not thrilled about how we're forcing reporters to funnel everything through a platform they may not want to interact with.

If I look up a store in my local area and they insist on making me use Facebook to see further information about them, most of the time I'll just move on. If the Linux Foundation helpdesk wants me to use JIRA to interact with them then I'll choose not to interact with them. If I need to use Bugzilla to file a bug report on your project then I'll nope on out of there. Where the transaction cost is higher than the care-factor, reporters will just opt out.

@mcollina
Copy link
Member

Considering the problems we had in the past, I think this is ok.

@yous
Copy link
Contributor

yous commented Apr 16, 2019

@nodejs/nodejs-ko Review please. Just updated to follow changes of security.md.

@marocchino
Copy link
Contributor

@yous LGTM

locale/en/security.md Outdated Show resolved Hide resolved
@reedloden reedloden merged commit f3be19b into nodejs:master Apr 16, 2019
@reedloden reedloden deleted the remove-security-email branch April 16, 2019 22:47
ghost pushed a commit that referenced this pull request Apr 19, 2019
ghost pushed a commit that referenced this pull request Apr 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Issues/pr concerning content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing PGP key
9 participants