| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: Federico G. Schwindt <fgsch@olimpo.com.br>
|
|
|
|
| |
fixing them.
|
|
|
|
| |
server says it's ok.
|
|
|
|
|
|
|
| |
there's an ``Ident'' field in the MS-CHAP2-Response and
MS-CHAP-Error attributes.
The RADIATOR server seems to be guilty of this.
|
|
|
|
| |
Only display message hook values we understand.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
additional label from ppp.linkup & ppp.linkdown to load.
Suggested and mostly submitted by: andrew pavlov <and@kremenchug.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Obtained from: OpenBSD
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sufficient.
In fact, using both breaks the radiator RADIUS daemon when used with
a db as it maps both attributes to the same field value and then
fails the insert.
I decided to remove RAD_NAS_IP_ADDRESS on the basis that rfc2138 says:
An Access-Request MUST contain a User-Name attribute. It SHOULD
contain either a NAS-IP-Address attribute or NAS-Identifier
attribute (or both, although that is not recommended). It MUST
despite the fact that this not recommended bit was removed from the
updated rfc.
|
|
|
|
| |
Suggested by: Theo de Raadt <deraadt@openbsd.org>
|
| |
|
|
|
|
|
|
| |
in our headers.
Submitted by: bde
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
/usr/src/usr.sbin/ppp/cbcp.c:566:61: warning: trigraph ??! ignored
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
just send PROTO_IP packets when we've got only one link up in multi-link
mode.
Problem noted by: Adrian Close <adrian@fernhilltec.com.au>
MFC after: 1 week
|
| |
|
|
|
|
| |
netinet/in.h.
|
|
|
|
| |
the inclusion of arpa/inet.h
|
| |
|
|
|
|
|
|
| |
Add support for Reply-Message and MS-CHAP-Error.
Sponsored by: Monzoon
|
|
|
|
|
|
|
|
|
|
| |
inbound queue.
Submitted by: "Amit K. Rao" <arao@niksun.com>
PR: 37813
MFC after: 1 week
Also fix a typo while I'm here.
|
|
|
|
|
|
| |
Store the Filter-Id attribute (we don't do anything with it yet)
Submitted mostly by: andrew pavlov <and@kremenchug.net>
|
| |
|
|
|
|
|
|
|
| |
point in being allowed to ``set mru'' for the MP lcp layer.
Spotted by: Richard Browne <richb@timestone.com.au>
MFC after: 1 month
|
| |
|
|
|
|
|
|
|
| |
the request as TLD may initialise fields that are set when decoding the
request.
MFC after: 1 week
|
| |
|
|
|
|
|
| |
Also change one case of blatant __progname abuse (several more remain)
This commit does not touch anything in src/{contrib,crypto,gnu}/.
|
|
|
|
|
|
|
| |
fails and on loss of carrier, the device doesn't become selectable with
0 bytes to read.
Problem reported by: ache
|
|
|
|
|
| |
IPPACKETSOUT, IPV6OCTETSIN, IPV6OCTETSOUT, IPV6PACKETSIN, IPV6PACKETSOUT,
OCTETSIN, OCTETSOUT, PACKETSIN, PACKETSOUT and SOCKNAME.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
instead of u_char *.
The changes are cosmetic except:
RecvConfigAck() now displays the options that are being ACK'd
Huge (bogus) options sent from the peer won't cause an infinite loop
SendIdent and ReceiveIdent are displayed consistenlty with other FSM data
LCP AUTHPROTO options that aren't understood are NAK'd, not REJ'd
|
|
|
|
|
|
| |
tun0.
Submitted by: qhwt@myrealbox.com
|
|
|
|
|
|
| |
255.255.255.254 as client ipaddr.
Reviewed-By: freebsd-net mailing list
|
| |
|