openbsd - A mirror of https://github.com/libressl/openbsd.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove unused sparc CPU capability detection code.	jsing	2024-10-19	1	-101/+0
\| \| \| \| \| \| \|	This has been unused for a long time - it can be found in the attic if someone wants to clean it up and enable it in the future. ok tb@
*	Remove non-visible and unused OPENSSL_wipe_cpu and OPENSSL_atomic_add	miod	2023-01-17	1	-201/+0
\| \| \| \| \| \| \|	interfaces, and remove empty assembly OPENSSL_cpuid_setup routines - the default empty C fallback will work as good. ok jsing@
*	spelling fixes; from paul tagliamonte	jmc	2022-12-26	1	-1/+1
\| \| \| \| \| \| \|	i removed the arithmetics -> arithmetic changes, as i felt they were not clearly correct ok tb
*	Remove oh-so-important-from-a-security-pov OpenSSL_rtdsc() function.	miod	2014-04-17	1	-17/+0
\|
*	Ok, there was a need for OPENSSL_cleanse() instead of bzero() to prevent	miod	2014-04-17	1	-83/+0
\| \| \| \| \| \| \| \| \| \| \|	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?
*	Import OpenSSL 1.0.1g	miod	2014-04-13	1	-2/+2
\|
*	import OpenSSL 1.0.0e	djm	2011-11-03	1	-1/+83
\|
*	import OpenSSL-1.0.0a	djm	2010-10-01	1	-19/+100
\|
*	import of OpenSSL 0.9.8h	djm	2008-09-06	1	-0/+239