- 09 Aug, 2004 2 commits
-
-
Richard Levitte authored
-
Richard Levitte authored
-
- 06 Aug, 2004 1 commit
-
-
Dr. Stephen Henson authored
-
- 05 Aug, 2004 2 commits
-
-
Dr. Stephen Henson authored
-
Dr. Stephen Henson authored
-
- 02 Aug, 2004 1 commit
-
-
Richard Levitte authored
Thanks to Dr Stephen Henson <shenson@drh-consultancy.co.uk> for making me aware of this error.
-
- 30 Jul, 2004 1 commit
-
-
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.
-
- 29 Jul, 2004 2 commits
-
-
Richard Levitte authored
the fips subdirectory, not the crypto one...
-
Richard Levitte authored
-
- 28 Jul, 2004 2 commits
-
-
Richard Levitte authored
name is defined. Go up one directory level before dealing with FIPS stuff.
-
Richard Levitte authored
-
- 27 Jul, 2004 6 commits
-
-
Dr. Stephen Henson authored
cipher suite is FIPS compatible. New cipherstring "FIPS" is all FIPS compatible ciphersuites except eNULL. Only allow FIPS ciphersuites in FIPS mode.
-
Richard Levitte authored
-
Richard Levitte authored
static variable
-
Dr. Stephen Henson authored
-
Dr. Stephen Henson authored
-
Dr. Stephen Henson authored
-
- 24 Jul, 2004 1 commit
-
-
Andy Polyakov authored
will either be optimized away or never performed. The trouble is that compiler first parses code, then optimizes, not both at once...
-
- 23 Jul, 2004 1 commit
-
-
Ben Laurie authored
-
- 22 Jul, 2004 1 commit
-
-
Andy Polyakov authored
-
- 21 Jul, 2004 3 commits
-
-
Dr. Stephen Henson authored
avoid use of prohibited MD5 algorithm.
-
Dr. Stephen Henson authored
-
Andy Polyakov authored
-
- 19 Jul, 2004 1 commit
-
-
Richard Levitte authored
instead of local time.
-
- 17 Jul, 2004 3 commits
-
-
Andy Polyakov authored
-
Andy Polyakov authored
we were mislead by _MSC_VER macro, which is defined by *all* Windows Microsoft compilers.
-
Andy Polyakov authored
compilers, e.g. DEC C.
-
- 12 Jul, 2004 3 commits
-
-
Ben Laurie authored
-
Richard Levitte authored
-
Bodo Möller authored
-
- 11 Jul, 2004 1 commit
-
-
Bodo Möller authored
-
- 08 Jul, 2004 1 commit
-
-
Richard Levitte authored
_stricmp() on that platform, use the appropriate header file for it, <string.h>. o_str.h: we only want to get size_t, which is defined in <stddef.h>. Philippe Bougeret <philippe.bougeret@freesbee.fr> notified us about Windows not having a <strings.h>
-
- 06 Jul, 2004 2 commits
-
-
Dr. Stephen Henson authored
-
Dr. Stephen Henson authored
-
- 04 Jul, 2004 1 commit
-
-
Dr. Stephen Henson authored
-
- 01 Jul, 2004 2 commits
-
-
Dr. Stephen Henson authored
-
Richard Levitte authored
Add a note as to how these functions do not always return the key size, and how one can deal with that. PR: 907
-
- 28 Jun, 2004 3 commits
-
-
Richard Levitte authored
PR: 499
-
Richard Levitte authored
-
Richard Levitte authored
there's no need for a larger BUFSIZE any more... PR: 904
-