The branch master has been updated
via bd23ccf616b48786b915a72d0f1c345dc74c503a (commit)
from 7daefd9fb8ada1fb5c919d27217cb39ffcd12ca3 (commit)
- Log -----------------------------------------------------------------
commit bd23ccf616b48786b915a72d0f1c345dc74c503a
Author: Rich Salz <rs...@akamai.com>
Date: Thu Sep 3 09:27:23 2015 -0400
Fix UserGuide.pdf links
-----------------------------------------------------------------------
Summary of changes:
docs/fipsnotes.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/fipsnotes.html b/docs/fipsnotes.html
index 7d66084..c3726b1 100644
--- a/docs/fipsnotes.html
+++ b/docs/fipsnotes.html
@@ -9,7 +9,7 @@
<article>
<header><h2>Important Notes about OpenSSL and FIPS 140</h2></header>
<div class="entry-content">
- <p>Please please read the <a href="UserGuide.pdf">User Guide</a>.
+ <p>Please please read the <a href="fips/UserGuide.pdf">User
Guide</a>.
Nothing will make sense otherwise (it still may not afterwards,
but at least you've a better chance).</p>
@@ -20,7 +20,7 @@
<p>Ok, so your company needs FIPS validated cryptography to land
that big sale, and your product currently uses OpenSSL. You
haven't worked up the motivation to wade through the entire <a
- href="UserGuide.pdf">User Guide</a> and want the quick "executive
+ href="fips/UserGuide.pdf">User Guide</a> and want the quick
"executive
summary". Here is a grossly oversimplified account:</p>
<p>
@@ -91,7 +91,7 @@
href="http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf";>Security
Policy</a>
and <a href="/source/openssl-fips-2.0.tar.gz">source</a>
at a minimum. And did we mention the
- <a href="UserGuide.pdf">User Guide</a>?</p>
+ <a href="fips/UserGuide.pdf">User Guide</a>?</p>
<h3>Performance at Startup</h3>
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits
