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.

Sign up for GitHub

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

Jump to bottom

Develop a security policy #8

Open
dstebila opened this issue Feb 3, 2024 · 3 comments
Open

Develop a security policy #8

dstebila opened this issue Feb 3, 2024 · 3 comments
Assignees
@planetf1

Comments

@dstebila
Copy link
Contributor

dstebila commented Feb 3, 2024

No description provided.

@planetf1
Copy link
Contributor

planetf1 commented Mar 11, 2024 •
edited
Loading

As part of this

  • a private mailing list will likely be needed (see lists.pqca.org - need to decide project-specific, pqca level, or both)
  • update SECURITY.md across all repos (to point to the authoritative link)

@TheFoxAtWork
Copy link

The following templates may be useful in setting this up:

It covers @planetf1 's points and then some.

@planetf1
Copy link
Contributor

At the TSC meeting held 2023-05-23 We agreed to

  • Create a SECURITY.md in each repository
  • Enable github private security vulnerability reporting

@planetf1 planetf1 self-assigned this May 26, 2024
@planetf1 planetf1 moved this to Backlog in TSC tracking Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@planetf1 planetf1

Labels
None yet
Projects
TSC tracking
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@planetf1 @dstebila @TheFoxAtWork