PrivateCoffee/security.private.coffee
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
security.private.coffee/security.txt

19 lines
651 B
Text
Raw Permalink Normal View History

feat(security): add security.txt for reporting issues Introduced a security.txt file to provide a standard way for security researchers to report vulnerabilities. The file specifies contact information, preferred languages, and encryption details for secure communication. This addition aligns with best practices for open-source projects, enhancing our project's security posture. - Establishes a clear communication channel for security issues. - Encourages responsible disclosure by providing encryption options. - Helps to streamline the vulnerability reporting process. This change is in line with the security recommendations for modern web services and applications.
2024-03-15 09:46:36 +00:00
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Contact: mailto:support@private.coffee
Preferred-Languages: en, de
feat(security): Added policy and expiration details Enhanced the security.txt with the inclusion of a security policy link and set an expiration date for the document. This update promotes transparency and ensures that the information remains current and reliable, aligning with best practices for security communications. The security policy link provides stakeholders with clear guidelines on reporting and handling security issues, fostering an environment of trust and collaboration. Setting an expiration date on the document mandates regular reviews, ensuring the details are always up-to-date and reflective of the latest security posture.
2024-03-15 10:05:31 +00:00
Policy: https://security.private.coffee/
feat(security): add security.txt for reporting issues Introduced a security.txt file to provide a standard way for security researchers to report vulnerabilities. The file specifies contact information, preferred languages, and encryption details for secure communication. This addition aligns with best practices for open-source projects, enhancing our project's security posture. - Establishes a clear communication channel for security issues. - Encourages responsible disclosure by providing encryption options. - Helps to streamline the vulnerability reporting process. This change is in line with the security recommendations for modern web services and applications.
2024-03-15 09:46:36 +00:00
Encryption: https://security.private.coffee/security@private.coffee.pub
Canonical: https://security.private.coffee/security.txt
Signed by: https://security.private.coffee/security@private.coffee.pub
feat(security): Added policy and expiration details Enhanced the security.txt with the inclusion of a security policy link and set an expiration date for the document. This update promotes transparency and ensures that the information remains current and reliable, aligning with best practices for security communications. The security policy link provides stakeholders with clear guidelines on reporting and handling security issues, fostering an environment of trust and collaboration. Setting an expiration date on the document mandates regular reviews, ensuring the details are always up-to-date and reflective of the latest security posture.
2024-03-15 10:05:31 +00:00
Expires: 2024-04-30T23:59:59.999Z
feat(security): add security.txt for reporting issues Introduced a security.txt file to provide a standard way for security researchers to report vulnerabilities. The file specifies contact information, preferred languages, and encryption details for secure communication. This addition aligns with best practices for open-source projects, enhancing our project's security posture. - Establishes a clear communication channel for security issues. - Encourages responsible disclosure by providing encryption options. - Helps to streamline the vulnerability reporting process. This change is in line with the security recommendations for modern web services and applications.
2024-03-15 09:46:36 +00:00
-----BEGIN PGP SIGNATURE-----
feat(security): Added policy and expiration details Enhanced the security.txt with the inclusion of a security policy link and set an expiration date for the document. This update promotes transparency and ensures that the information remains current and reliable, aligning with best practices for security communications. The security policy link provides stakeholders with clear guidelines on reporting and handling security issues, fostering an environment of trust and collaboration. Setting an expiration date on the document mandates regular reviews, ensuring the details are always up-to-date and reflective of the latest security posture.
2024-03-15 10:05:31 +00:00
iI4EARYIADYWIQR8+ffWeJVvJW3sPVIzxXDbF7H3lgUCZfQdMhgcc2VjdXJpdHlA
cHJpdmF0ZS5jb2ZmZWUACgkQM8Vw2xex95aGvwEAoG82M23pnpry5+LyW6JxbU7q
daeBFEUWtovZs6YPP7AA/3NThooJJVP9uQ/7QjfnXr2BE72Yeh6fUffT6AvCqIcC
=wUNM
feat(security): add security.txt for reporting issues Introduced a security.txt file to provide a standard way for security researchers to report vulnerabilities. The file specifies contact information, preferred languages, and encryption details for secure communication. This addition aligns with best practices for open-source projects, enhancing our project's security posture. - Establishes a clear communication channel for security issues. - Encourages responsible disclosure by providing encryption options. - Helps to streamline the vulnerability reporting process. This change is in line with the security recommendations for modern web services and applications.
2024-03-15 09:46:36 +00:00
-----END PGP SIGNATURE-----
Reference in a new issue Copy permalink