1. 14 Oct, 2004 3 commits
  2. 08 Oct, 2004 1 commit
  3. 04 Oct, 2004 2 commits
  4. 01 Oct, 2004 1 commit
  5. 28 Sep, 2004 2 commits
  6. 15 Sep, 2004 1 commit
  7. 13 Sep, 2004 2 commits
  8. 11 Sep, 2004 1 commit
  9. 10 Sep, 2004 2 commits
  10. 06 Sep, 2004 2 commits
  11. 23 Aug, 2004 1 commit
  12. 18 Aug, 2004 1 commit
  13. 11 Aug, 2004 3 commits
  14. 10 Aug, 2004 4 commits
  15. 09 Aug, 2004 2 commits
  16. 06 Aug, 2004 1 commit
  17. 05 Aug, 2004 2 commits
  18. 02 Aug, 2004 1 commit
  19. 30 Jul, 2004 1 commit
    • Richard Levitte's avatar
      To protect FIPS-related global variables, add locking mechanisms · 7f9c3745
      Richard Levitte authored
      around them.
      
      NOTE: because two new locks are added, this adds potential binary
      incompatibility with earlier versions in the 0.9.7 series.  However,
      those locks will only ever be touched when FIPS_mode_set() is called
      and after, thanks to a variable that's only changed from 0 to 1 once
      (when FIPS_mode_set() is called).  So basically, as long as FIPS mode
      hasn't been engaged explicitely by the calling application, the new
      locks are treated as if they didn't exist at all, thus not becoming a
      problem.  Applications that are built or rebuilt to use FIPS
      functionality will need to be recompiled in any case, thus not being a
      problem either.
      7f9c3745
  20. 29 Jul, 2004 2 commits
  21. 28 Jul, 2004 2 commits
  22. 27 Jul, 2004 3 commits