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

	Commit message (Collapse)	Author	Age	Files	Lines
*	don't permit freeaddrinfo(NULL). now the behavior is consistent	itojun	2000-01-28	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \|	across {free,net,open}bsd. both rfc2553 and X/Open spec are silent about the behavior, and there's no strong consensus either. i think library should NOT be forgiving in this case, to promote development of more robust 3rd-party codebase (code works on "freeaddrinfo(NULL) = SEGV" will work on "freeaddrinfo(NULL) is okay" environment, but not the other way around). only issue i have now is NRL freeaddrinfo() compatibility, which permits freeaddrinfo(NULL).
*	avoid memory leakage on freeaddrinfo().	itojun	2000-01-27	1	-0/+2
\| \| \| \|	(this bug was introduced since we mix KAME getaddrinfo and NRL freeaddrinfo).
*	KNF	deraadt	1999-06-23	1	-7/+9
\|
*	Added some protocol independent interfaces (supposedly IPv6 support APIs, but	cmetz	1999-06-23	1	-0/+45
	ones that are useful for all protocols, not just IPv6).