Have 'make clean' clean away the log files.

[openssl.git] / README.FIPS

diff --git a/README.FIPS b/README.FIPS
index 686308fcef30f07a7004b687fd41698962fa595f..c41bab99307bfc71bc69ea876e6640b68b099667 100644 (file)
--- a/README.FIPS
+++ b/README.FIPS
@@ -1,7 +1,7 @@
 Preliminary status and build information for FIPS module v2.0
 
 Preliminary status and build information for FIPS module v2.0
 

-NB: if you are cross compiling you now need to use the latest "incore2" script
-from http://www.openssl.org/docs/fips/incore2
+NB: if you are cross compiling you now need to use the latest "incore" script
+this can be found at util/incore in the tarballs.

 
 If you have any object files from a previous build do:
 
 
 If you have any object files from a previous build do:
 


@@ -9,11 +9,15 @@ make clean
 
 To build the module do:
 
 
 To build the module do:
 

-./config fipscanisterbuild
+./config fipscanisteronly

 make
 
 Build should complete without errors.
 
 make
 
 Build should complete without errors.
 

+Build test utilities:
+
+make build_tests
+

 Run test suite:
 
 test/fips_test_suite
 Run test suite:
 
 test/fips_test_suite


@@ -23,7 +27,7 @@ again should complete without errors.
 Run test vectors: 
 
 1. Download an appropriate set of testvectors from www.openssl.org/docs/fips
 Run test vectors: 
 
 1. Download an appropriate set of testvectors from www.openssl.org/docs/fips

-   those for 2007 are OK.
+   only the fips-2.0 testvector files are usable for complete tests.

 
 2. Extract the files to a suitable directory.
 
 
 2. Extract the files to a suitable directory.
 


@@ -35,6 +39,9 @@ Run test vectors:
 4. It should say "passed all tests" at the end. Report full details of any
    failures.
 
 4. It should say "passed all tests" at the end. Report full details of any
    failures.
 

+If you wish to use the older 1.2.x testvectors (for example those from 2007)
+you need the command line switch --disable-v2 to fipsalgtest.pl
+

 Examine the external symbols in fips/fipscanister.o they should all begin
 with FIPS or fips. One way to check with GNU nm is:
 
 Examine the external symbols in fips/fipscanister.o they should all begin
 with FIPS or fips. One way to check with GNU nm is:
 


@@ -117,8 +124,6 @@ reports.
 
 Known issues:
 
 
 Known issues:
 

-Algorithm tests are pre-2011.
-The fipslagtest.pl script wont auto run new algorithm tests such as DSA2.

 Code needs extensively reviewing to ensure it builds correctly on 
 supported platforms and is compliant with FIPS 140-2.
 The "FIPS capable OpenSSL" is still largely untested, it builds and runs
 Code needs extensively reviewing to ensure it builds correctly on 
 supported platforms and is compliant with FIPS 140-2.
 The "FIPS capable OpenSSL" is still largely untested, it builds and runs