1
0

README.txt 2.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. # Notes on the wolfssl-fips project
  2. First, if you did not get the FIPS files with your archive, you must contact
  3. wolfSSL to obtain them.
  4. The IDE/WIN/wolfssl-fips.sln solution is for the original FIPS #2425 certificate.
  5. See IDE/WIN10/wolfssl-fips.sln for the FIPS v2 #3389 or later Visual Studio solution.
  6. # Building the wolfssl-fips project
  7. The wolfCrypt FIPS library for Windows is a part of the wolfSSL library. It
  8. must be built as a static library, for the moment.
  9. The library project is built with Whole Program Optimization disabled. This is
  10. required so that necessary components of the library are not optimized away.
  11. There are two functions added to the library that are used as markers in
  12. memory for the in-core memory check of the code. WPO consolidates them into a
  13. single function. WPO also optimizes away the automatic FIPS entry function.
  14. Each of the source files inside the FIPS boundary defines their own code and
  15. constant section. The code section names start with ".fipsA$" and the constant
  16. section names start with ".fipsB$". Each subsection has a letter to organize
  17. them in a specific order. This specific ordering puts marker functions and
  18. constants on either end of the boundary so it can be hashed.
  19. # In Core Memory Test
  20. The In Core Memory test calculates a checksum (HMAC-SHA256) of the wolfCrypt
  21. FIPS library code and constant data and compares it with a known value in
  22. the code.
  23. The Randomized Base Address setting needs to be disabled on the 32-bit builds
  24. but can be enabled on the 64-bit builds. In the 32-bit mode the addresses
  25. being different throws off the in-core memory calculation. It looks like in
  26. 64-bit mode the library uses all offsets, so the core hash calculation
  27. is the same every time.
  28. The "verifyCore" check value in the source fips_test.c needs to be updated when
  29. building the code. The POS performs this check and the default failure callback
  30. will print out the calculated checksum. When developing your code, copy this
  31. value and paste it back into your code in the verifyCore initializer then
  32. rebuild the code. When statically linking, you may have to recalculate your
  33. check value when changing your application.
  34. # Build Options
  35. The default build options should be the proper default set of options:
  36. * HAVE_FIPS
  37. * HAVE_THREAD_LS
  38. * HAVE_AESGCM
  39. * HAVE_HASHDRBG
  40. * WOLFSSL_SHA384
  41. * WOLFSSL_SHA512
  42. * NO_HC128
  43. * NO_RC4
  44. * NO_RABBIT
  45. * NO_DSA
  46. * NO_MD4
  47. The "NO" options explicitly disable algorithms that are not allowed in
  48. FIPS mode.
  49. Additionally one may enable:
  50. * HAVE_ECC
  51. * OPENSSL_EXTRA
  52. * WOLFSSL_KEY_GEN
  53. These settings are defined in IDE/WIN/user_settings.h.