From 1676bec94c079610a3fa2324ccd5f878bc18b1dc Mon Sep 17 00:00:00 2001 From: "Dr. Stephen Henson" Date: Tue, 30 Mar 2010 16:35:41 +0000 Subject: update FAQ --- FAQ | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'FAQ') diff --git a/FAQ b/FAQ index 1f77e47843..ff58e4fc9d 100644 --- a/FAQ +++ b/FAQ @@ -134,7 +134,7 @@ OpenSSL. Information on the OpenSSL mailing lists is available from * Where can I get a compiled version of OpenSSL? You can finder pointers to binary distributions in -http://www.openssl.org/related/binaries.html . + . Some applications that use OpenSSL are distributed in binary form. When using such an application, you don't need to install OpenSSL @@ -466,7 +466,7 @@ administrators. Other projects do have other policies so you can for example extract the CA bundle used by Mozilla and/or modssl as described in this article: - http://www.mail-archive.com/modssl-users@modssl.org/msg16980.html + [BUILD] ======================================================================= @@ -508,7 +508,7 @@ when you run the test suite (using "make test"). The message returned is "bc: 1 not implemented". The best way to deal with this is to find another implementation of bc -and compile/install it. GNU bc (see http://www.gnu.org/software/software.html +and compile/install it. GNU bc (see for download instructions) can be safely used, for example. @@ -519,7 +519,7 @@ that the OpenSSL bntest throws at it. This gets triggered when you run the test suite (using "make test"). The message returned is "bc: stack empty". The best way to deal with this is to find another implementation of bc -and compile/install it. GNU bc (see http://www.gnu.org/software/software.html +and compile/install it. GNU bc (see for download instructions) can be safely used, for example. @@ -723,13 +723,13 @@ list. * 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 -tracker. This can be done my mailing the report to rt@openssl.org (or its alias -openssl-bugs@openssl.org), please note that messages sent to the request -tracker also appear in the public openssl-dev mailing list. +tracker. This can be done my mailing the report to (or its +alias ), please note that messages sent to the +request tracker also appear in the public openssl-dev mailing list. The report should be in plain text. Any patches should be sent as plain text attachments because some mailers corrupt patches sent inline. -If your issue affects multiple versions of OpenSSL check any patch apply +If your issue affects multiple versions of OpenSSL check any patches apply cleanly and, if possible include patches to each affected version. The report should be given a meaningful subject line briefly summarising the @@ -738,17 +738,17 @@ issue. Just "bug in OpenSSL" or "bug in OpenSSL 0.9.8n" is not very helpful. By sending reports to the request tracker the bug can then be given a priority and assigned to the appropriate maintainer. The history of discussions can be accessed and if the issue has been addressed or a reason why not. If patches -are sent to openssl-dev instead only they can be lost if a team member has to +are only sent to openssl-dev they can be mislaid if a team member has to wade through months of old messages to review the discussion. -See also http://www.openssl.org/support/rt.html +See also * I've found a security issue, how do I report it? If you think your bug has security implications then please send it to openssl-security@openssl.org if you don't get a prompt reply at least acknowledging receipt then resend or mail it directly to one of the -more active team members (e.g. steve@openssl.org). +more active team members (e.g. Steve). [PROG] Questions about programming with OpenSSL -- cgit v1.2.3