Revision tags: release/14.0.0 |
|
#
b3e76948 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
#
4d846d26 |
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
#
1de7b4b8 |
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
show more ...
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
d4d4a70a |
| 25-May-2007 |
Roman Bogorodskiy <novel@FreeBSD.org> |
Add a new option for ppp.conf: rad_port_id. It allows to change the way of what ppp submits to the RADIUS server as NAS-Port-Id. Possible options are: the PID of the process owning the corresponding
Add a new option for ppp.conf: rad_port_id. It allows to change the way of what ppp submits to the RADIUS server as NAS-Port-Id. Possible options are: the PID of the process owning the corresponding interface, tun(4) interface number, interface index (as it would get returned by if_nametoindex(3)), or it's possible to keep the default behavior. Check the ppp(8) manual page for details.
PR: bin/112764 Submitted by: novel (myself) Reviewed by: flz Approved by: flz MFC after: 1 month
show more ...
|
Revision tags: release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0 |
|
#
88044778 |
| 27-Jan-2005 |
Brian Somers <brian@FreeBSD.org> |
Add a radius_Flush() function that waits for the response (or timeout) to any pending RADIUS transaction. Use this before sending RAD_STOP RADIUS messages so that we definitely ``stop'' the session.
Add a radius_Flush() function that waits for the response (or timeout) to any pending RADIUS transaction. Use this before sending RAD_STOP RADIUS messages so that we definitely ``stop'' the session.
It was discovered that sometimes when the link timed out, we got lucky enough to have an un-ACK'd RADIUS accounting transaction in progress, resulting in the RAD_STOP message failing to send.
Original report found on: A russion news group Text translated by: glebius Tested by: Alexey Popov llp at iteranet dot com MFC after: 7 days
show more ...
|
Revision tags: release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0 |
|
#
e715b13b |
| 17-Jul-2004 |
Brian Somers <brian@FreeBSD.org> |
Support a ``set rad_alive N'' command to enable periodic RADIUS accounting information being sent to the RADIUS server.
Logging of RADIUS accounting information moves to a ``set log [+-]radius'' lev
Support a ``set rad_alive N'' command to enable periodic RADIUS accounting information being sent to the RADIUS server.
Logging of RADIUS accounting information moves to a ``set log [+-]radius'' level, along with the RADIUS alive info, and the version number is bumped to 3.2 to reflect this.
Mostly submitted by: alx@sm.ukrtel.net (back in January) MFC after: 3 weeks
show more ...
|
Revision tags: release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0 |
|
#
2cc2a59d |
| 28-Jun-2003 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
name union.
|
#
ec3e98b8 |
| 20-Jun-2003 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
IPV6PREFIX is set when Framed-IPv6-Prefix is defined, You may want to pass the value to upper layer protocol such as DHCPv6 for prefix delegation.
MFC after: 1 week
|
#
cf7c10d0 |
| 19-Jun-2003 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
Do RADIUS accounting on IPV6CP.
MFC after: 1 week
|
#
8bfaa57b |
| 19-Jun-2003 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
Oops, I put unused variable in my previous commit.
MFC after: 1 week
|
#
0fe74aa4 |
| 19-Jun-2003 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
Install routes specified by Framed-IPv6-Route. Since the format of Framed-IPv6-Route is user defined, it follows Framed-IP-route.
MFC after: 1 week
|
Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs |
|
#
250be50b |
| 17-Jun-2002 |
Brian Somers <brian@FreeBSD.org> |
Compensate for dodgy Win98/WinME MSCHAPv2 responses later in the code path... after we've talked to any RADIUS servers involved, so that we haven't touched the data before it gets to the server.
Mak
Compensate for dodgy Win98/WinME MSCHAPv2 responses later in the code path... after we've talked to any RADIUS servers involved, so that we haven't touched the data before it gets to the server.
Make it clearer in the code that this compensation is done by setting a flag to a value of zero, a flag which rfc2759 says *MUST* be zero.
While we're here, don't bother passing the peer challenge into radius_Authenticate(). It's already part of the key we're passing in (this becomes obvious now that I've structured that data...).
This ``fix'' doesn't help to authenticate Win98/WinME users in my test environment as ports/net/freeradius seems to ignore the flag completely anyway, but it may help with other RADIUS servers.
show more ...
|
#
10be78d3 |
| 15-Jun-2002 |
Brian Somers <brian@FreeBSD.org> |
Remove whitespace at the end of lines.
|
#
8fb5ef5a |
| 12-Jun-2002 |
Brian Somers <brian@FreeBSD.org> |
Understand the following Microsoft Vendor Specific RADIUS attributes:
RAD_MICROSOFT_MS_MPPE_ENCRYPTION_POLICY RAD_MICROSOFT_MS_MPPE_ENCRYPTION_TYPES RAD_MICROSOFT_MS_MPPE_RECV_KEY RAD_MICROS
Understand the following Microsoft Vendor Specific RADIUS attributes:
RAD_MICROSOFT_MS_MPPE_ENCRYPTION_POLICY RAD_MICROSOFT_MS_MPPE_ENCRYPTION_TYPES RAD_MICROSOFT_MS_MPPE_RECV_KEY RAD_MICROSOFT_MS_MPPE_SEND_KEY
These attributes may be supplied by a RADIUS server when MSCHAPv2 is used to authenticate.
It *should* now be possible to build ppp with -DNODES and still support CHAP/MSCHAP/MSCHAPv2/MPPE via a RADIUS server, but the code isn't yet smart enough to do that (building with -DNODES just looses these facilities).
Sponsored by: Monzoon
show more ...
|
#
a16061b2 |
| 16-May-2002 |
Brian Somers <brian@FreeBSD.org> |
Handle MS-CHAPv2 authentication correctly via the RADIUS server (if it's configured). Handle internal failures in radius_Authenticate() correctly. Bump the ppp version number.
This doesn't yet work
Handle MS-CHAPv2 authentication correctly via the RADIUS server (if it's configured). Handle internal failures in radius_Authenticate() correctly. Bump the ppp version number.
This doesn't yet work with MPPE. More will follow.
Sponsored by: Mozoon
show more ...
|
#
ff8e577b |
| 10-May-2002 |
Brian Somers <brian@FreeBSD.org> |
Add support for MS-CHAP authentication via a RADIUS server. Add support for Reply-Message and MS-CHAP-Error.
Sponsored by: Monzoon
|
#
bf1eaec5 |
| 07-May-2002 |
Brian Somers <brian@FreeBSD.org> |
Understand the Session-Timeout RADIUS attribute Store the Filter-Id attribute (we don't do anything with it yet)
Submitted mostly by: andrew pavlov <and@kremenchug.net>
|
#
33b47634 |
| 04-Apr-2002 |
Tatsumi Hosokawa <hosokawa@FreeBSD.org> |
Get tun P2P address from the local pool if RADIUS server returned 255.255.255.254 as client ipaddr.
Reviewed-By: freebsd-net mailing list
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs, release/4.3.0_cvs, release/4.3.0 |
|
#
50ca6ec3 |
| 02-Apr-2001 |
Brian Somers <brian@FreeBSD.org> |
Don't assume challenges and responses don't contain embedded '\0's.
Mschapv2 response generation may produce embedded NULs... causing us to send a bogus response to the radius server and end up fail
Don't assume challenges and responses don't contain embedded '\0's.
Mschapv2 response generation may produce embedded NULs... causing us to send a bogus response to the radius server and end up failing the client's valid response.
Problem pointed out by: Eugene Vigovskiy <vigov@com2com.ru>
show more ...
|
#
52847614 |
| 09-Mar-2001 |
Brian Somers <brian@FreeBSD.org> |
MAXPATHLEN -> PATH_MAX Don't assume MAXHOSTNAMELEN includes the NUL Correct a diagnostic Use "localhost" in our prompt instead of ""
|
Revision tags: release/4.2.0, release/4.1.1_cvs |
|
#
794c9bbc |
| 29-Aug-2000 |
Brian Somers <brian@FreeBSD.org> |
Support radius accounting, and add a packet count to throughput statistics as a side effect.
Submitted by: Marcin Cieslak <saper@system.pl>
with some tweaks to RAD_ACCT_SESSION_ID and RAD_ACCT_MULT
Support radius accounting, and add a packet count to throughput statistics as a side effect.
Submitted by: Marcin Cieslak <saper@system.pl>
with some tweaks to RAD_ACCT_SESSION_ID and RAD_ACCT_MULTI_SESSION_ID generation by me.
show more ...
|
Revision tags: release/4.1.0, release/3.5.0_cvs, release/4.0.0_cvs |
|
#
f013f33e |
| 14-Mar-2000 |
Brian Somers <brian@FreeBSD.org> |
To avoid namespace polution in NetBSD:
``struct descriptor'' -> ``struct fdescriptor''
|
Revision tags: release/3.4.0_cvs, release/3.3.0_cvs |
|
#
97d92980 |
| 28-Aug-1999 |
Peter Wemm <peter@FreeBSD.org> |
$Id$ -> $FreeBSD$
|
Revision tags: release/3.2.0, release/3.1.0 |
|
#
f0cdd9c0 |
| 06-Feb-1999 |
Brian Somers <brian@FreeBSD.org> |
Decouple pap & chap output routines from the corresponding input routines and take advantage of the new init/continue interface in libradius. This allows a timely response on other links in an MP se
Decouple pap & chap output routines from the corresponding input routines and take advantage of the new init/continue interface in libradius. This allows a timely response on other links in an MP setup while RADIUS requests are in progress as well as the ability to handle other data from the peer in parallel. It should also make the future addition of PAM support trivial.
While I'm in there, validate pap & chap header IDs if ``idcheck'' is enabled (the default) for other FSM packet types.
NOTE: This involved integrating the generation of chap challenges and the validation of chap responses (and commenting what's going on in those routines). I currently have no way of testing ppps ability to respond to M$Chap CHALLENGEs correctly, so if someone could do the honours, it'd be much appreciated (it *looks* ok!).
Sponsored by: Internet Business Solutions Ltd., Switzerland
show more ...
|
#
972a1bcf |
| 28-Jan-1999 |
Brian Somers <brian@FreeBSD.org> |
Initial RADIUS support (using libradius). See the man page for details. Compiling with -DNORADIUS (the default for `release') removes support.
TODO: The functionality in libradius::rad_send_reques
Initial RADIUS support (using libradius). See the man page for details. Compiling with -DNORADIUS (the default for `release') removes support.
TODO: The functionality in libradius::rad_send_request() needs to be supplied as a set of routines so that ppp doesn't have to wait indefinitely for the radius server(s). Instead, we need to get a descriptor back, select() on the descriptor, and ask libradius to service it when necessary. For now, ppp blocks SIGALRM while in rad_send_request(), so it misses PAP/CHAP retries & timeouts if they occur.
Only PAP is functional. When CHAP is attempted, libradius complains that no User-Password has been specified... rfc2138 says that it *mustn't* be used for CHAP :-(
Sponsored by: Internet Business Solutions Ltd., Switzerland
show more ...
|