Don't cross-post security advisories to oss-security
authorMatt Caswell <matt@openssl.org>
Thu, 23 Mar 2023 13:34:01 +0000 (13:34 +0000)
committerTomas Mraz <tomas@openssl.org>
Thu, 4 May 2023 08:17:18 +0000 (10:17 +0200)
commit85972a475ef91042e6be0eda4db3202ccc6d0fd2
tree81168a74b4673fb1fb01f9fcda2ee2206b7f73e4
parent3ab47885e9e684c4311d5c8d138069485d087cd1
Don't cross-post security advisories to oss-security

We should send any security advisory to oss-security separately and not
cross-post it with our own lists.

We also change the text to say that security advisories should be sent to
support-announce regardless of whether a premium release has been affected.

Reviewed-by: Paul Dale <pauli@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/tools/pull/139)
HOWTO-make-a-release.md