summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/bn (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Stop being a dummy... presumably these are left overs from pedantic modejsing2014-05-151-2/+0
| | | | | | that were not wrapped with #if PEDANTIC. ok miod@
* knfectomie.jsing2014-05-081-653/+818
|
* Emergency knfectomie requested by tedu@.jsing2014-05-0830-6133/+6618
|
* with the first bug it uncovered fixed, clear all bignums again.tedu2014-05-071-17/+9
| | | | i've never worked on codebase so resistant to efforts to improve it.
* in BN_clear_free, don't cleanse the data if the static data flag is set.tedu2014-05-071-3/+2
| | | | | | | | much debugging work done by otto. ok miod otto. side note: BN_FLG_STATIC_DATA doesn't actually mean the data is static. it's also used to indicate the data may be secretly shared behind your back as a sort of poor man's refcounting, but without the refcounting.
* revert, thanks sthentedu2014-05-071-9/+17
|
* inspired by a cloudflare diff, cleanse old memory when expanding a bignum.tedu2014-05-051-17/+9
| | | | | | however, instead of trying to audit all the places where a secret bignum is used, apply the big hammer and clear all bignums when freed. ok deraadt miod
* typosmiod2014-05-031-2/+2
|
* More use of 64-bit registers which needs to be disabled under OpenBSD.miod2014-05-021-0/+2
|
* Do not output SOM-specific directives.miod2014-05-011-0/+6
|
* Fix include filename to get register name aliases under BSDmiod2014-05-011-6/+1
|
* Pass -Werror in the !BN_LLONG !BN_UMULT_LOHI !BN_UMULT_HIGH case.miod2014-05-011-4/+4
|
* dead meatmiod2014-05-012-2528/+0
|
* First pass at removing win64 support from the assembly generating Perljsing2014-04-302-286/+0
| | | | | | | scripts. We certainly do not need an identical copy of the win64 exception handler in each script (surely one copy would be sufficient). ok miod@
* Remove WIN32, WIN64 and MINGW32 tentacles.miod2014-04-282-10/+1
| | | | | | | | Also check for _LP64 rather than __arch64__ (the former being more reliable than __LP64__ or __arch64__) to tell 64-bit int platforms apart from 32-bit int platforms. Loosely based upon a diff from Martijn van Duren on tech@
* Try to clean the maze of <openssl/bn.h> defines regarding the BN internals.miod2014-04-2410-227/+25
| | | | | | | | | | | | | | | | | | | | | | | The intent of this change is to only keep support for two kind of architectures: - those with 32-bit int and long, and 64-bit long long, where ``long * long -> long long'' multiplication routines are available. - those with 64-bit int and long, and no 128-bit long long type. This gets rid of the SIXTY_FOUR_BIT_LONG, SIXTY_FOUR_BIT (not the same!), THIRTY_TWO_BIT, SIXTEEN_BIT and EIGHT_BIT defines. After this change, the types and defines are as follows: arch: 64bit 32bit rationale BN_LLONG undefined defined defined if l * l -> ll BN_ULLONG undefined u long long result of BN_LONG * BN_LONG BN_ULONG u long u int native register size BN_LONG long int the same, signed BN_BITS 128 64 size of 2*BN_ULONG in bits BN_BYTES 8 4 size of 2*BN_ULONG in bytes BN_BITS2 64 32 BN_BITS / 2 Tested on various 32-bit and 64-bit OpenBSD systems of various endianness.
* One last Dec C tentacle on alpha.miod2014-04-231-4/+1
|
* When I grow up, I want to write workaround for long long multiplicationsmiod2014-04-231-15/+0
| | | | under __TANDEM systems and compilers, using hardcoded octal numbers. NOT.
* Remove IRIX_CC_BUG workaround.miod2014-04-231-6/+0
|
* I'm glad to know that Ultrix CC has a bug optimizing switch() statementsmiod2014-04-231-5/+0
| | | | | lacking an explicit `case 0:' construct. But Ultrix has been dead for more than 15 years, really. Don't give it any reason to move out of its coffin.
* Unifdef -UPEDANTIC. ok beck@ tedu@miod2014-04-232-2/+2
|
* Remove meat which either duplicates code found in apps/, or is only of valuemiod2014-04-224-661/+0
| | | | for 20th century historians, and can be put in the Attic.
* theo found a file we don't seem to need, but just in case, i will pastetedu2014-04-201-3/+0
| | | | | | the contents below: #!/usr/local/bin/perl # x86 assember
* Lacking a proof that--for this implementation--exposure of Montgomeryguenther2014-04-192-7/+7
| | | | | | | | multiplication or RSA blinding parameters doesn't permit retroactive timing analysis of the secrets, we'll do the stupidly cheap thing and cleanse them before freeing them. ok deraadt@
* We'll interpret a (void) cast on snprintf() to mean it's been verified thatguenther2014-04-191-4/+4
| | | | | | truncation is either desirable, not an issue, or is detected and handled later ok deraadt@
* Do not ask the user to pass either -DB_ENDIAN or -DL_ENDIAN to the compiler,miod2014-04-181-1/+3
| | | | | | | but rather figure out the endianness from <machine/endian.h> automagically; help from guenther@ ok jca@ guenther@ beck@ and the rest of the `Buena SSL rampage club'
* Get rid of MS Visual C compiler and Intel C compiler specific defines.miod2014-04-171-9/+0
|
* Nuke BN_DEBUG_LEVITTEmiod2014-04-171-10/+0
|
* todo: do not leave 15 year old todo lists in the tree.miod2014-04-171-3/+0
|
* Use of OPENSSL_SYS_xxx defines in public header files considered harmful.miod2014-04-171-6/+1
|
* Change library to use intrinsic memory allocation functions instead ofbeck2014-04-179-42/+42
| | | | | | | | OPENSSL_foo wrappers. This changes: OPENSSL_malloc->malloc OPENSSL_free->free OPENSSL_relloc->realloc OPENSSL_freeFunc->free
* RAND_seed now does nothing, so skip the operationderaadt2014-04-171-6/+0
|
* we don't use these files for buildingtedu2014-04-151-179/+0
|
* remove FIPS mode support. people who require FIPS can buy something thattedu2014-04-151-4/+0
| | | | | meets their needs, but dumping it in here only penalizes the rest of us. ok beck deraadt
* Go home, VMS, you're drunkmiod2014-04-152-6508/+0
|
* No licence.miod2014-04-151-41/+0
|
* Moved to regress/lib/libcrypto.miod2014-04-152-2217/+0
|
* Part 1 of eliminating BIO_snprintf(). This fixes mechanical conversionsbeck2014-04-151-4/+4
| | | | | where the return value is ignored changing to (void) snprintf. ok deraadt@
* So the OpenSSL codebase does "get the time, add it as a random seed"deraadt2014-04-141-3/+0
| | | | | | | in a bunch of places inside the TLS engine, to try to keep entropy high. I wonder if their moto is "If you can't solve a problem, at least try to do it badly". ok miod
* remove auto-generated dependencies from the old unused build system, soderaadt2014-04-141-196/+0
| | | | | that it is easier to find code pieces. They are getting in the way. ok miod
* replace PTR_SIZE_INT (only used for VMS) with uintptr_t, tweaks from jca@,sthen2014-04-143-54/+32
| | | | makes sense to beck@
* Merge conflicts; remove MacOS, Netware, OS/2, VMS and Windows build machinery.miod2014-04-136-26/+106
|
* This commit was generated by cvs2git to track changes on a CVS vendormiod2014-04-137-32/+36
|\ | | | | branch.
| * Import OpenSSL 1.0.1gmiod2014-04-1314-75/+150
| |
* | cherry pick bugfixes for http://www.openssl.org/news/secadv_20130205.txtmarkus2013-02-141-17/+8
| | | | | | | | | | from the openssl git (changes between openssl 1.0.1c and 1.0.1d). ok djm@
* | import files that CVS missed; sighdjm2012-10-131-0/+272
| |
* | resolve conflictsdjm2012-10-1312-491/+734
| |
* | This commit was generated by cvs2git to track changes on a CVS vendordjm2012-10-1316-248/+10473
|\| | | | | branch.
| * import OpenSSL-1.0.1cdjm2012-10-1326-732/+11172
| |
* | OpenSSL 1.0.0f: mergedjm2012-01-051-14/+23
| |
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-22 02:13:53 +0000