[openssl-commits] [web] master update

[Rich Salz]

The branch master has been updated
       via  513aa39c856bcd2f1248451222056ac0b420e900 (commit)
      from  754b4f4d892bbaaf333bb5a0be2078e80b5927d2 (commit)


- Log -----------------------------------------------------------------
commit 513aa39c856bcd2f1248451222056ac0b420e900
Author: Viktor Szakats <vszakats at users.noreply.github.com>
Date:   Tue Aug 18 15:05:36 2015 +0200

    FAQ: use https URLs
    
    Signed-off-by: Rich Salz <rsalz at akamai.com>

-----------------------------------------------------------------------

Summary of changes:
 docs/faq.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/faq.txt b/docs/faq.txt
index f4356a7..85b8092 100644
--- a/docs/faq.txt
+++ b/docs/faq.txt
@@ -481,7 +481,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:
-<URL: http://www.mail-archive.com/modssl-users@modssl.org/msg16980.html>
+<URL: https://www.mail-archive.com/modssl-users@modssl.org/msg16980.html>
 
 
 * Some secure servers 'hang' with OpenSSL 1.0.1, is this a bug?
@@ -532,7 +532,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 <URL: http://www.gnu.org/software/software.html>
+and compile/install it.  GNU bc (see <URL: https://www.gnu.org/software/software.html>
 for download instructions) can be safely used, for example.