picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
Systemd/docs/SECURITY.md

12 lines
588 B
Markdown
Raw Normal View History

docs: create new SECURITY.md page github has special support for that name: https://help.github.com/en/articles/adding-a-security-policy-to-your-repository.
2019-08-30 11:45:42 +02:00
---
docs: uppercase all markdown document titles For most we used uppercasing, but not for all. Let's stick to one rule, and uppercase them all.
2020-01-14 10:14:11 +01:00
title: Reporting of Security Vulnerabilities
docs: place all our markdown docs in rough categories
2019-12-11 10:49:28 +01:00
category: Contributing
docs: make it pretty Add custom Jekyll theme, logo, webfont and .gitignore FIXME: the markdown files have some H1 headers which need to be replaced with H2
2019-12-11 17:01:46 +01:00
layout: default
docs: create new SECURITY.md page github has special support for that name: https://help.github.com/en/articles/adding-a-security-policy-to-your-repository.
2019-08-30 11:45:42 +02:00
---
docs: uppercase all markdown document titles For most we used uppercasing, but not for all. Let's stick to one rule, and uppercase them all.
2020-01-14 10:14:11 +01:00
# Reporting of Security Vulnerabilities
docs: create new SECURITY.md page github has special support for that name: https://help.github.com/en/articles/adding-a-security-policy-to-your-repository.
2019-08-30 11:45:42 +02:00
docs: reorder the section about security reporting to emphasize the sekrit list
2020-04-29 08:09:53 +02:00
If you discover a security vulnerability, we'd appreciate a non-public disclosure. systemd developers can be contacted privately on the **[systemd-security@redhat.com](mailto:systemd-security@redhat.com) mailing list**. The disclosure will be coordinated with distributions.
(The [issue tracker](https://github.com/systemd/systemd/issues) and [systemd-devel mailing list](https://lists.freedesktop.org/mailman/listinfo/systemd-devel) are fully public.)
Reference in a new issue Copy permalink