OWEALs/openssl

Autor	SHA1 Mensaxe	Data
Ben Laurie	a51a97262d Brought forward from 0.9.8 - 64 bit warning fixes and fussy compiler fixes.	%!s(int64=19) %!d(string=hai) anos
Richard Levitte	9426364be9 Typo	%!s(int64=19) %!d(string=hai) anos
Richard Levitte	b172dec864 DEC C complains about bad subscript, but we know better, so let's shut it up.	%!s(int64=19) %!d(string=hai) anos
Nils Larsch	fcb41c0ee8 rewrite of bn_nist.c, disable support for some curves on 64 bit platforms	%!s(int64=19) %!d(string=hai) anos
Geoff Thorpe	b6358c89a1 Convert openssl code not to assume the deprecated form of BN_zero().	%!s(int64=20) %!d(string=hai) anos
Geoff Thorpe	a8aa764d3c Minimise the amount of code dependent on BN_DEBUG_RAND. In particular,	%!s(int64=20) %!d(string=hai) anos
Andy Polyakov	27b2b78f90 Even though C specification explicitly says that constant type "stretches"	%!s(int64=20) %!d(string=hai) anos
Geoff Thorpe	0ef85c7f45 This is a revert of my previous commit to "improve" the declaration of	%!s(int64=21) %!d(string=hai) anos
Ulf Möller	078dd1a0f9 typo in comment	%!s(int64=21) %!d(string=hai) anos
Geoff Thorpe	d870740cd7 Put the first stage of my bignum debugging adventures into CVS. This code	%!s(int64=21) %!d(string=hai) anos
Geoff Thorpe	c465e7941e This is the least unacceptable way I've found for declaring the bignum data	%!s(int64=21) %!d(string=hai) anos
Geoff Thorpe	31166ec8f3 Some provisional bignum debugging has begun to detect inconsistent BIGNUM	%!s(int64=21) %!d(string=hai) anos
Bodo Möller	19b8d06a79 clean up new code for NIST primes	%!s(int64=22) %!d(string=hai) anos
Bodo Möller	5c6bf03117 fast reduction for NIST curves	%!s(int64=22) %!d(string=hai) anos

Commit History Buscar

Commit History