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

Provide improved security/bug-reporting disclosure instructions #1

Closed
grctest opened this issue Aug 24, 2017 · 8 comments
Closed

Provide improved security/bug-reporting disclosure instructions #1

grctest opened this issue Aug 24, 2017 · 8 comments

Comments

@grctest
Copy link
Contributor

grctest commented Aug 24, 2017

From @grctest on August 15, 2017 20:42

Due to a lack of communication & established security disclosure instructions, several security researchers have published rather negative research against Gridcoin citing a lack of communication/attention by the devs.

Ideally, we should not promote contact@gridcoin.us as the main contact point as this isn't a team email account but rather monitored by Rob (who in this scenario allegedly ignored/missed the researchers subsequent emails).

We should route researchers towards Slack's #development channel, or instruct them to contact an admin/op/mod on irc/telegram/slack/cryptocointalk. Had the researchers reached out via chat, they would have had more attention paid to them by many users.

Copied from original issue: grctest/Gridcoin-Site#70

@grctest
Copy link
Contributor Author

grctest commented Aug 24, 2017

From @jring-o on August 15, 2017 22:31

Thank you for getting this moving CM!

I think a clearly marked "Security Disclosure" section under a "contact" page will do wonders for Gridcoin development and reputation.

For those who do not wish to use slack, we could direct them to a specific e-mail, perhaps multidev, perhaps not, whatever structure we want.

While we're at it, what if we set up more direct communication channels for other types of contact:

Media
Marketing
Development
Business Proposals
Partnerships
Researchers (for people who want to make projects with BOINC and fund them with GRC but don't know where to start, for example)

and whatever else we can come up with.

This will break up contact so no 1 person must deal with all the different e-mail GRC receives. If these are added to a General@gridcoin (or whatever) e-mail, it will also act as a natural filter for people asking random questions and people with specific intent.

@grctest
Copy link
Contributor Author

grctest commented Aug 24, 2017

From @barton2526 on August 16, 2017 0:26

I can put a PR in immediately which changes the "Contact Us" link in the footer to a link to the dev slack channel. If anyone has any other suggestions, such as having multiple points of contact (Contact Us Page), let me know and I will edit the PR.

It's up. #71

@grctest
Copy link
Contributor Author

grctest commented Aug 24, 2017

From @barton2526 on August 16, 2017 1:38

#72 adds to header

@grctest
Copy link
Contributor Author

grctest commented Aug 31, 2017

I've added a 'contact us' page which details the multiple methods of reaching admins/community, as well as some security issue reporting instructions. Think this is sufficient, or should the contact us page be expanded?

@grctest
Copy link
Contributor Author

grctest commented Sep 22, 2017

Need to reference @TheCharlatan's security procedure document.

barton2526 added a commit that referenced this issue Sep 25, 2017
@barton2526
Copy link
Member

@barton2526
Copy link
Member

@barton2526
Copy link
Member

Added in #60

barton2526 pushed a commit that referenced this issue May 30, 2019
RoboticMind pushed a commit that referenced this issue Sep 11, 2021
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

No branches or pull requests

2 participants