| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is Solar Designers implementation from
http://openwall.info/wiki/people/solar/software/public-domain-source-code/md5 .
RS_MD5Transform goes away since it's not in md5.h. It's not used in
lib/radius/.
Might want to move this into lib/radius/ if we end up not using it in
lib/.
|
| |
|
|
|
|
| |
And distribute LICENSE and HACKING.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
lib/configure.ac
lib/include/radsec/radsec.h
lib/radius/client.h
|
| | |
|
| | |
|
|/
|
|
|
| |
Should really have been done as part of bumping the library version
(0.0.2.dev in configure.ac).
|
| |
|
| |
|
|
|
|
|
|
|
| |
A new API for attributes will be added once we've decided how to deal
with RADIUS packets internally. For now, removing the half baked
wrapping seems more sensible than trying to free rs_attr objects and
their VALUE_PAIR's.
|
| |
|
| |
|
|
|
|
| |
Also, move copyright notice out of COPYING and into every file.
|
|
|
|
| |
Sending, no retransmitting and no receiving.
|
|
|
|
|
| |
Move peer (former server) things to new file peer.c.
Update examples.
|
|
|
|
|
|
|
|
| |
'timeout' and 'tries' move from 'server' stanza to top. 'tries' is
now 'retries'.
Moving around in internal data structs, making struct peer strictly config.
Bug fixes in configuration code.
Adding some more cleanup code, freeing allocated memory (still not done!).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
NOTE: Clean up of resources not yet sane. Expect resource leakages.
NOTE: Most failure cases are not handled properly. With the wind at
your back and the sun shining, it might work.
|
| |
|
| |
|
| |
|
|
|