mirror of
https://github.com/openssl/openssl.git
synced 2025-02-23 14:42:15 +08:00
Tweak README about rt and bug reporting.
Reviewed-by: Matt Caswell <matt@openssl.org>
This commit is contained in:
parent
14815a99d5
commit
932af1617e
33
README
33
README
@ -137,17 +137,23 @@
|
|||||||
|
|
||||||
Email the report to:
|
Email the report to:
|
||||||
|
|
||||||
openssl-bugs@openssl.org
|
rt@openssl.org
|
||||||
|
|
||||||
Note that the request tracker should NOT be used for general assistance
|
In order to avoid spam, this is a moderated mailing list, and it might
|
||||||
or support queries. Just because something doesn't work the way you expect
|
take a day for the ticket to show up. (We also scan posts to make sure
|
||||||
does not mean it is necessarily a bug in OpenSSL.
|
that security disclosures aren't publically posted by mistake.) Mail to
|
||||||
|
this address is recorded in the public RT (request tracker) database (see
|
||||||
|
https://www.openssl.org/support/rt.html for details) and also forwarded
|
||||||
|
the public openssl-dev mailing list. Confidential mail may be sent to
|
||||||
|
openssl-security@openssl.org (PGP key available from the key servers).
|
||||||
|
|
||||||
Note that mail to openssl-bugs@openssl.org is recorded in the public
|
Please do NOT use this for general assistance or support queries.
|
||||||
request tracker database (see https://www.openssl.org/support/rt.html
|
Just because something doesn't work the way you expect does not mean it
|
||||||
for details) and also forwarded to a public mailing list. Confidential
|
is necessarily a bug in OpenSSL.
|
||||||
mail may be sent to openssl-security@openssl.org (PGP key available from
|
|
||||||
the key servers).
|
You can also make GitHub pull requests. If you do this, please also send
|
||||||
|
mail to rt@openssl.org with a link to the PR so that we can more easily
|
||||||
|
keep track of it.
|
||||||
|
|
||||||
HOW TO CONTRIBUTE TO OpenSSL
|
HOW TO CONTRIBUTE TO OpenSSL
|
||||||
----------------------------
|
----------------------------
|
||||||
@ -164,11 +170,10 @@
|
|||||||
reason as to why that feature isn't implemented.
|
reason as to why that feature isn't implemented.
|
||||||
|
|
||||||
Patches should be as up to date as possible, preferably relative to the
|
Patches should be as up to date as possible, preferably relative to the
|
||||||
current Git or the last snapshot. They should follow the coding style of
|
current Git or the last snapshot. They should follow our coding style
|
||||||
OpenSSL and compile without warnings. Some of the core team developer targets
|
(see http://openssl.org/about/codingstyle.txt) and compile without
|
||||||
can be used for testing purposes, (debug-steve64, debug-geoff etc). OpenSSL
|
warnings using the --strict-warnings flag. OpenSSL compiles on many
|
||||||
compiles on many varied platforms: try to ensure you only use portable
|
varied platforms: try to ensure you only use portable features.
|
||||||
features.
|
|
||||||
|
|
||||||
Note: For legal reasons, contributions from the US can be accepted only
|
Note: For legal reasons, contributions from the US can be accepted only
|
||||||
if a TSU notification and a copy of the patch are sent to crypt@bis.doc.gov
|
if a TSU notification and a copy of the patch are sent to crypt@bis.doc.gov
|
||||||
|
Loading…
Reference in New Issue
Block a user