| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=326276
|
| |
|
|
| |
Notes:
svn path=/head/; revision=134789
|
| |
|
|
|
|
|
| |
PR: 31771
Notes:
svn path=/head/; revision=122440
|
| |
|
|
|
|
|
| |
string.
Notes:
svn path=/head/; revision=100916
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=98311
|
| |
|
|
| |
Notes:
svn path=/head/; revision=98243
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
RAD_MICROSOFT_MS_CHAP_ERROR and RAD_MICROSOFT_MS_CHAP2_SUCCESS
messages, and remove the hack in chap.c to ignore that ident field
on the client side.
This anomoly was hacked around during development, and I forgot to
go back and fix it properly.
Spotted by: Sergey Korolew <ds@rt.balakovo.ru>
Notes:
svn path=/head/; revision=98149
|
| |
|
|
| |
Notes:
svn path=/head/; revision=96731
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=96730
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Bump version number to 3.0.4
o When talking to a RADIUS server, provide a NAS-Port-Type.
When the NAS-Port-Type is Ethernet, provide a NAS-Port value equal
to the SESSIONID from the environment in direct mode or the
NGM_PPPOE_SESSIONID message in other modes. If no SESSIONID is found,
default to the interface index in client mode or zero in server mode.
When the NAS-Port-Type is ISDN, set the NAS-Port to the minor number
of the physical device (ie, the N in /dev/i4brbchN).
This makes it easier for the RADIUS server to identify the client
WRT accounting data etc.
Prompted by: lsz8425 <lsz8425@mail.cd.hn.cn>
Notes:
svn path=/head/; revision=96582
|
| |
|
|
|
|
|
|
|
| |
Add support for Reply-Message and MS-CHAP-Error.
Sponsored by: Monzoon
Notes:
svn path=/head/; revision=96324
|
| |
|
|
|
|
|
|
|
|
|
| |
discipline to do the async escaping, but no other benefits are available yet.
Change ``ifdef HAVE_DES'' to ``ifndef NODES'' for consistency.
Make the Makefile a little more sane WRT RELEASE_CRUNCH.
Notes:
svn path=/head/; revision=93418
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
structures (well, they're treated as opaque).
It's now possible to manage IPv6 interface addresses and routing
table entries and to filter IPV6 traffic whether encapsulated or
not.
IPV6CP support is crude for now, and hasn't been tested against
any other implementations.
RADIUS and IPv6 are independent of eachother for now.
ppp.linkup/ppp.linkdown aren't currently used by IPV6CP
o Understand all protocols(5) in filter rules rather than only a select
few.
o Allow a mask specification for the ``delete'' command. It's now
possible to specifically delete one of two conflicting routes.
o When creating and deleting proxy arp entries, do it for all IPv4
interface addresses rather than doing it just for the ``current''
peer address.
o When iface-alias isn't in effect, don't blow away manually (via ``iface
add'') added interface addresses.
o When listening on a tcp server (diagnostic) socket, bind so that a
tcp46 socket is created -- allowing both IPv4 and IPv6 connections.
o When displaying ICMP traffic, don't display the icmp type twice.
When display traffic, display at least some information about unrecognised
traffic.
o Bump version
Inspired after filtering work by: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
Notes:
svn path=/head/; revision=81634
|
| |
|
|
| |
Notes:
svn path=/head/; revision=81094
|
| |
|
|
| |
Notes:
svn path=/head/; revision=81066
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When encryption (MPPE) is enabled, WindowsME and Windows98 both
fail because of the extra byte, suggesting that they autheticated
successfully in their log and then dropping the connection, telling
the user that the peer doesn't support compatible encryption
options.
MFC after: 1 week
Notes:
svn path=/head/; revision=80763
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
byte of the packet to contain '\0'.
Windows 98 gets this wrong, dropping garbage into the last byte and
failing authentication.
Now, we notice this and whinge to our log file that we're compensating
for the corrupt data.
Notes:
svn path=/head/; revision=80721
|
| |
|
|
|
|
|
| |
Approved by: Toshiharu OHNO <tohno@sirius.ocn.ne.jp>
Notes:
svn path=/head/; revision=78189
|
| |
|
|
|
|
|
|
|
|
|
| |
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>
Notes:
svn path=/head/; revision=75071
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MPPE session keys correctly.
I'm a bit dubious about this code. It seems that the session keys
are initialised differently based on whether you're the client or
the server. One side is the server if it issues the first challenge,
but of course you can issue a challenge from both sides.... at the
same time. Sounds like another wonderful M$ assumption...
Ppp can now talk to itself correctly using encryption.
Problem solved by: Ustimenko Semen <semen@iclub.nsu.ru>
Hair torn out by: me
Notes:
svn path=/head/; revision=68461
|
| |
|
|
|
|
|
| |
Make some functions static.
Notes:
svn path=/head/; revision=67912
|
| |
|
|
|
|
|
| |
Submitted by: Ustimenko Semen <semen@iclub.nsu.ru>
Notes:
svn path=/head/; revision=67910
|
| |
|
|
|
|
|
| |
capabilities.
Notes:
svn path=/head/; revision=64802
|
| |
|
|
|
|
|
| |
be doubled up to mean a single literaly ``!''.
Notes:
svn path=/head/; revision=64465
|
| |
|
|
|
|
|
| |
Two new commands are available; ``ident'' and ``sendident''.
Notes:
svn path=/head/; revision=63484
|
| |
|
|
|
|
|
| |
``struct descriptor'' -> ``struct fdescriptor''
Notes:
svn path=/head/; revision=58028
|
| |
|
|
| |
Notes:
svn path=/head/; revision=55253
|
| |
|
|
|
|
|
| |
Pointed out by: billf
Notes:
svn path=/head/; revision=55252
|
| |
|
|
|
|
|
| |
Submitted by: Rich Neswold <rneswold@MCS.Net>
Notes:
svn path=/head/; revision=55146
|
| |
|
|
|
|
|
| |
The entire command is ignored if the syntax is invalid...
Notes:
svn path=/head/; revision=54914
|
| |
|
|
| |
Notes:
svn path=/head/; revision=54912
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(LCP/CCP/IPCP), one for urgent IP traffic and one for
everything else.
o Add the ``set urgent'' command for adjusting the list of
urgent port numbers. The default urgent ports are 21, 22,
23, 513, 514, 543 and 544 (Ports 80 and 81 have been
removed from the default priority list).
o Increase the buffered packet threshold from 20 to 30.
o Report the number of packets in the IP output queue and the
list of urgent ports under ``show ipcp''.
Notes:
svn path=/head/; revision=50867
|
| |
|
|
| |
Notes:
svn path=/head/; revision=50479
|
| |
|
|
|
|
|
| |
exec()ing other programs.
Notes:
svn path=/head/; revision=49976
|
| |
|
|
| |
Notes:
svn path=/head/; revision=48817
|
| |
|
|
|
|
|
| |
Problem reported by: Amedeo Beck Peccoz <gea@gressoney.it>
Notes:
svn path=/head/; revision=47849
|
| |
|
|
|
|
|
|
|
|
|
| |
o Show more information about missing MP fragments in ``show mp''.
o Do away with mbuf_Log(). It was showing mbuf stats twice on
receipt of LCP/CCP/IPCP packets.... ???!!?
o Pre-allocate a bit extra when creating LQR packets to avoid having
to allocate another mbuf in mbuf_Prepend().
Notes:
svn path=/head/; revision=47695
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the layering.
We now ``stack'' layers as soon as we open the device (when we figure
out what we're dealing with). A static set of `dispatch' routines are
also declared for dealing with incoming packets after they've been
`pulled' up through the stacked layers.
Physical devices are now assigned handlers based on the device type
when they're opened. For the moment there are three device types;
ttys, execs and tcps.
o Increment version number to 2.2
o Make an entry in [uw]tmp for non-tty -direct invocations (after
pap/chap authentication).
o Make throughput counters quad_t's
o Account for the absolute number of mbuf malloc()s and free()s in
``show mem''.
o ``show modem'' becomes ``show physical''.
Notes:
svn path=/head/; revision=46686
|
| |
|
|
|
|
|
|
|
|
|
| |
receiver and one for the sender. This allows two simultaneous
chap conversations - something that I *thought* I was already
doing on a daily basis myself until the existence of the
problem was
Beaten into me by: sos
Notes:
svn path=/head/; revision=45907
|
| |
|
|
|
|
|
| |
phase.
Notes:
svn path=/head/; revision=45220
|
| |
|
|
|
|
|
|
|
| |
Some CHAP implementations send no welcome message with their
SUCCESS/FAILURE packets. This was being mis-identified as
a truncated packet by the new authentication code :-(
Notes:
svn path=/head/; revision=44159
|
| |
|
|
| |
Notes:
svn path=/head/; revision=44123
|
| |
|
|
|
|
|
| |
chap 0x80.
Notes:
svn path=/head/; revision=44122
|
| |
|
|
|
|
|
| |
authenticator and authenticatee.
Notes:
svn path=/head/; revision=44106
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
each time rather than making up a new one.
Increase the authname/authkey max sizes to 100 characters.
Allow ``authkey'' specifications beginning with ``!''.
When a challenge is received, the text following the
``!'' is executed as a program (expanding stuff in the same
way that ``sh'' and ``!bg'' do). The program is passed the
peer name, peer challenge and local ``authname'' on standard
input and is expected to output the name/key combination that
should be used to build the CHAP response.
This provides support for Secure ID cards (guess what I was
given at work recently!) using CHAP.
Examples will follow.
Notes:
svn path=/head/; revision=43888
|
| |
|
|
|
|
|
| |
(broken with last commit).
Notes:
svn path=/head/; revision=43743
|
| |
|
|
| |
Notes:
svn path=/head/; revision=43742
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=43693
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
configured. This isn't strictly necessary according to the
rfc, but it's suggested there....
o Don't forget to include our authname when sending a
CHAP challenge when RADIUS is configured.
o Don't supply the ``16'' representing the chap answer
length to radius_Authenticate() - libradius does this
for us.
o When we successfully authenticate via radius_Authenticate(),
continue with datalink_AuthOk() as expected.
Sponsored by: Internet Business Solutions Ltd., Switzerland
Notes:
svn path=/head/; revision=43401
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=43313
|