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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Send OPENSSL_issetugid() straight to hell, no final cigarette.	deraadt	2015-04-11	1	-12/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The issetugid() API is supposed to make a strong promise where "0 means it is safe to look at the environment". Way back in the past someone on the OpenSSL team responded to the environment access danger by creating a wrapper called OPENSSL_issetugid, and went to use it a number of places. However, by default on systems lacking true issetugid(), OPENSSL_issetugid returns 0. 0 indicating safely. False safety. Which means OPENSSL_issetugid() fails to make any sort of promise about safety, in fact it is just the opposite. Can you believe the OpenSSL team? This nastiness was noticed over the years, however noone could gain traction and get it fixed in OpenSSL. Also see a paragraph about this in http://www.tedunangst.com/flak/post/worst-common-denominator-programming ok jsing
*	tags as requested by miod and tedu	deraadt	2014-06-12	1	-0/+1
\|
*	remove include files not needed	deraadt	2014-04-18	1	-16/+2
\|
*	Remove wraparounds for operating systems which lack issetugid().	deraadt	2014-04-15	1	-81/+15
\| \| \| \| \| \| \|	I will note that some were missing, looking at you Solaris!!! Anyone home? Using my own copyright on the file now, since this is a rewrite of a trivial wrapper around a system call I invented. ok beck
*	First pass at applying KNF to the OpenSSL code, which almost makes it	jsing	2014-04-15	1	-14/+16
\| \| \| \| \|	readable. This pass is whitespace only and can readily be verified using tr and md5.
*	resolve conflicts	djm	2008-09-06	1	-1/+1
\|
*	merge 0.9.7b with local changes; crank majors for libssl/libcrypto	markus	2003-05-12	1	-1/+1
\|
*	OpenSSL 0.9.7 stable 2002 05 08 merge	beck	2002-05-15	1	-3/+4
\|
*	openssl-engine-0.9.6a merge	beck	2001-06-22	1	-0/+88