summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Remove support for big-endian i386 and amd64.miod2014-04-176-44/+2
| | | | | | | | | | | | | Before someone suggests the OpenSSL people are junkies, here is what they mention about this: /* Most will argue that x86_64 is always little-endian. Well, * yes, but then we have stratus.com who has modified gcc to * "emulate" big-endian on x86. Is there evidence that they * [or somebody else] won't do same for x86_64? Naturally no. * And this line is waiting ready for that brave soul:-) */ So, yes, they are on drugs. But they are not alone, the stratus.com people are, too.
* since we're replacing LIST_SEPARATOR_CHAR with ':', no point using %csthen2014-04-171-1/+1
| | | | in the help printf
* Mostly gut e_os.h:deraadt2014-04-1759-134/+105
| | | | | | | | USE_SOCKETS is unrelated to using sockets, but just pulls in .h files. It makes every file buy a kitchen sink, because 11 files forgot to. EXIT() is really exit(), a gentle surprise but... OPENSSL_EXIT() is really just return(), because noone compiles the openssl command non-monolithic anymore
* malloc + memset 0 -> callocmiod2014-04-172-44/+4
| | | | | (not that it matters much as this is in disabled code, for we don't build with zlib support)
* dead codetedu2014-04-171-2/+0
|
* -Walltedu2014-04-173-3/+7
|
* unused variabletedu2014-04-172-6/+2
|
* a little less obfuscationtedu2014-04-172-34/+4
|
* fold prototypes into o_str.c. miodtedu2014-04-174-138/+8
|
* quick pass at removing ability to disable sha256 and sha512. ok miodtedu2014-04-1710-72/+0
|
* Aren't you glad to have this file tell you that ``C2.pl works''? Bonus pointmiod2014-04-172-2/+0
| | | | if you can spot C2.pl.
* Nuke BN_DEBUG_LEVITTEmiod2014-04-172-20/+0
|
* No need to consider being compiled by NASM anymore.miod2014-04-172-8/+0
|
* Stop paying lip service to non-AT&T syntax assemblers in the x86 world.miod2014-04-176-772/+2
|
* todo: do not leave 15 year old todo lists in the tree.miod2014-04-172-6/+0
|
* fix BIO_snprintf usage in here.beck2014-04-172-16/+38
| | | | ok tedu@
* Use of OPENSSL_SYS_xxx defines in public header files considered harmful.miod2014-04-179-102/+2
|
* Bob O.D.'ed on the o_dir code so high he forgot to rm the `test' aftermiod2014-04-172-132/+0
| | | | rewriting the code.
* sprintf: bad.miod2014-04-172-2/+2
| | | | | | snprintf: good. snprintf with a correct size: better! (harmless in this case)
* Remove utils that we don't useafresh12014-04-176-330/+0
| | | | | | | opensslwrap.sh and shlib_wrap.sh are used by tests that are getting replaced, x86asm.sh is obsoleted by our Makefile machinery ok miod
* Remove unused ssl utilsafresh12014-04-1760-11438/+0
| | | | | | This code is the reason perl has a name as a write only language. ok deraadt miod
* expunge more of the old build systemafresh12014-04-174-1199/+0
| | | | ok deraadt miod
* Remove oh-so-important-from-a-security-pov OpenSSL_rtdsc() function.miod2014-04-1724-502/+4
|
* fix some more leaks, mostly suggestions from miodjsg2014-04-1712-4/+28
| | | | ok miod@
* Remove the benchmark part of the selftest. It uses the undocumentedmiod2014-04-172-86/+0
| | | | | | | OPENSSL_rdtsc() routine to get a high-precision timestamp, and (although this is the only user of this routine in libcrypto) forces every platform willing to provide fast assembly versions of some routines, to also provide OPENSSL_rdtsc().
* crypto/modes/gcm128.c can be used as its own selftest. Add it to regress,miod2014-04-172-1/+14
| | | | conveniently leaving the benchmark code not compiled in the test.
* Ok, there was a need for OPENSSL_cleanse() instead of bzero() to preventmiod2014-04-1719-744/+2
| | | | | | | | | | | supposedly smart compilers from optimizing memory cleanups away. Understood. Ok, in case of an hypothetically super smart compiler, OPENSSL_cleanse() had to be convoluted enough for the compiler not to recognize that this was actually bzero() in disguise. Understood. But then why there had been optimized assembler versions of OPENSSL_cleanse() is beyond me. Did someone not trust the C obfuscation?
* Move the machine-specific parts of the libcrypto Makefile to per-arch makefilemiod2014-04-175-104/+242
| | | | | | fragments, to ease maintainance, and see through the fog of bugs. "looks good" deraadt@
* some KNF cleanup following the scriptderaadt2014-04-1744-338/+332
|
* Invoke OPENSSL_add_all_algorithms_noconf() to enforce OPENSSL_cpuid_setup()miod2014-04-171-5/+1
| | | | | has been called, for, depending how libcrypto, it might be a hidden symbol. Reported by jsg@
* fix some of the leaksjsg2014-04-178-14/+46
| | | | ok miod@ looks good deraadt@
* fix a potential double freejsg2014-04-172-4/+4
| | | | ok miod@
* remove OPENSSL_realloc_clean usage here - replace with intrinsics to makebeck2014-04-172-8/+14
| | | | | it obvious what should happen. ok tedu@
* Fully kill FIPS API. Forcible certification conflicts with the goals of atedu2014-04-175-158/+2
| | | | | | free software project. ok beck deraadt Ports calling FIPS_mode_set(1): mongodb
* Initial KNF.jsing2014-04-178-1016/+1010
|
* Initial KNF.jsing2014-04-174-502/+459
|
* Initial KNF.jsing2014-04-172-173/+133
|
* More KNF.jsing2014-04-172-11/+16
|
* More KNF.jsing2014-04-171-11/+17
|
* Initial KNF.jsing2014-04-171-329/+289
|
* I've replaced everything in this file. ISC liscense it with my copyrightbeck2014-04-172-108/+26
|
* Initial KNF.jsing2014-04-171-212/+214
|
* Remove defines for unwanted OS support...jsing2014-04-171-54/+0
| | | | ok miod@
* remove some code that is now unused after guenther's changes in 1.20.jsg2014-04-172-32/+2
|
* KNF.jsing2014-04-172-6/+6
|
* Initial KNF.jsing2014-04-176-278/+244
|
* simply wrap around intrinsics, and knf cleanup.beck2014-04-172-114/+108
| | | | ok miod@ deraadt@
* Change library to use intrinsic memory allocation functions instead ofbeck2014-04-17477-2618/+2618
| | | | | | | | OPENSSL_foo wrappers. This changes: OPENSSL_malloc->malloc OPENSSL_free->free OPENSSL_relloc->realloc OPENSSL_freeFunc->free
* Revert unintended whitespace changes.jsing2014-04-175-19/+19
|
* OPENSSL_gmtime() is not a gmtime() wrapper. It is a gmtime_r().deraadt2014-04-172-36/+8
| | | | | Always trying to confuse people... ok guenther
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-28 23:26:44 +0000