radsecproxy.git - RADIUS proxy with support for TLS RadSec

	Commit message (Collapse)	Author	Age	Files	Lines
*	WIP commit moving towards working server support.	Linus Nordberg	2013-05-15	1	-20/+22
\|
*	Revamping for listeners.	Linus Nordberg	2013-03-01	1	-12/+12
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Split rs_connection into rs_baseconn plus rs_connection and rs_listener. Connections now has a state variable. Connect buffer event and fd of _source_ connection, not that of conn->active_peer. The connection object referred to by a peer is not meant for using as a connection, only for reporting errors on. Make sure things are sane even when not using a config file. Bump library interface version to 1.0.0 since it's changed.
*	WIP commit for listener support.	Linus Nordberg	2013-02-19	1	-9/+9
\|
*	Remove dead code.libradsec-user-dispatch	Linus Nordberg	2013-01-28	1	-10/+0
\|
*	Rename most 'package' to 'message'.	Linus Nordberg	2013-01-24	1	-0/+265
	RADIUS (RFC2865) is defined to be transported over UDP so the term "radius packet" makes a lot of sense. RADIUS/TCP (RFC6613) and RADIUS/TLS (RFC6614), a.k.a. RadSec, use stream transport protocols though. The term "message" doesn't imply any kind of transport -- a message can be sent using datagrams as well as in a stream. This (large) commit changes 'package' to 'message' where it makes sense. It does not touch the 'radius' subdirectory. It includes preprocessor directives (#define) to make the public interface compatible with previous releases of the library.