Skip to content

Security contact incorrect #127

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

Open
2 tasks
quozl opened this issue Apr 19, 2025 · 4 comments
Open
2 tasks

Security contact incorrect #127

quozl opened this issue Apr 19, 2025 · 4 comments

Comments

@quozl
Copy link

quozl commented Apr 19, 2025

Reporting security issues through GitHub (such as via dependabot discovery) on this repository redirects to security@sugarlabs.org, which bounces.

Either;

Thanks.

@pikurasa
Copy link
Contributor

@chimosky what do you recommend?

@chimosky
Copy link
Member

chimosky commented Apr 24, 2025

Creating a new alias - security@sugarlabs.org - can work, but the question is, who do we want to see these alerts?

systems@lists.sugarlabs.org comes to mind, but I'm skeptical as most people on the list don't manage our GH repos, but it does give visibility to the issue.

If anyone is fine with receiving and looking into these issues then we can create an alias and have it point at them.

@quozl
Copy link
Author

quozl commented Apr 24, 2025

systems@lists.sugarlabs.org is public, archived, using that would violate the conventions on privacy of disclosure.

https://lists.sugarlabs.org/archive/systems/

It should be an office-bearer of the organisation, or one of their delegates.

Also remember to consider not having a GitHub security contact, requiring all disclosures to be public or to office-bearers in private.

@chimosky
Copy link
Member

systems@lists.sugarlabs.org is public, archived, using that would violate the conventions on privacy of disclosure.

https://lists.sugarlabs.org/archive/systems/

It should be an office-bearer of the organisation, or one of their delegates.

Also remember to consider not having a GitHub security contact, requiring all disclosures to be public or to office-bearers in private.

I agree, we can have someone on the board handle this.

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

3 participants