summaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorDr. Stephen Henson <steve@openssl.org>2013-11-11 14:40:07 +0000
committerDr. Stephen Henson <steve@openssl.org>2013-11-11 22:25:00 +0000
commit5fad2c93bc161ab387de5810d9fa15b42893f702 (patch)
tree21a75d50924efc391dac116d04f4b44a45353d42 /FAQ
parentd0f1d924adb1f53559528586d0894d580aa07506 (diff)
downloadopenssl-new-5fad2c93bc161ab387de5810d9fa15b42893f702.tar.gz
Update FAQ
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ6
1 files changed, 6 insertions, 0 deletions
diff --git a/FAQ b/FAQ
index e1b04a5288..9543e4ab07 100644
--- a/FAQ
+++ b/FAQ
@@ -738,6 +738,7 @@ never make sense, and tend to emerge when you least expect them. In order
to identify one, drop optimization level, e.g. by editing CFLAG line in
top-level Makefile, recompile and re-run the test.
+
* I think I've found a bug, what should I do?
If you are a new user then it is quite likely you haven't found a bug and
@@ -746,6 +747,11 @@ documentation and the mailing lists for similar queries. If you are still
unsure whether it is a bug or not submit a query to the openssl-users mailing
list.
+If you think you have found a bug based on the output of static analysis tools
+then please manually check the issue is genuine. Such tools can produce a
+LOT of false positives.
+
+
* I'm SURE I've found a bug, how do I report it?
Bug reports with no security implications should be sent to the request