| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
Reviewed by: fenner, wollman
Submitted by: luigi
|
|
|
|
|
|
|
| |
is a digit.
PR: bin/9484
Submitted by: Matthew D. Fuller <fullermd@futuresouth.com>
|
|
|
|
| |
Submitted by: charnier
|
|
|
|
| |
(broken with last commit).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Root Password entry (PR#9291 - Jack O'Neill).
|
|
|
|
|
| |
PR: 9871
Submitted by: Boris Popov <bp@butya.kz>
|
|
|
|
| |
into alphabetical order.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
Now we know which variables are internal and which need to be
backed to /etc/rc.conf.site. rc.conf is not touched now.
Also kget kernel change information back properly and set up a loader.rc
file to use it.
|
| |
|
| |
|
|
|
|
| |
Encouraged by: Nate
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously the foolowing lines would have broken:
controller fdc0 at isa? disable port ? bio
controller fdc0 at isa? disable port 0x100 bio
While this would work:
controller fdc0 at isa? disable port "IO_FD1" bio
The first of the three lines is useful for making placeholder devices
for PCMCIA-floppies, and the second is useful for non-standard hardware.
The failure is a "(null)" string in ioconf.c that the compiler pukes on.
Thanks to: Bruce Evans (bde@freebsd.org)
|
| |
|
|
|
|
|
|
|
| |
When NAKing the peer, get as close as we can to what
he REQd.
When the peer NAKs us, get as close as we can to what
they NAKd with on our next REQ.
|
|
|
|
|
| |
(if someone writes the other half). Also rewrite the man page in a more
appropriate (formal) style.
|
| |
|
|
|
|
|
| |
PR: 7454
Submitted by: Stefan Eggers <seggers@semyam.dinoco.de>
|
|
|
|
|
|
| |
the command line.
Revise the error diagnostics so that invalid labels
are reported immediately.
|
|
|
|
|
|
| |
at the authentication layer rather than at the PAP layer
so that it also applies to CHAP (no response to CHAP
challenges).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
the user is privileged.
I believe this should address both concerns in PR 9729, and may also
provide the desired behavior from PR 9485.
|
|
|
|
| |
values I'm going to use again. :-}
|
|
|
|
| |
requests, give up (don't sit there indefinitely).
|
|
|
|
|
|
|
| |
(2) Use 'device' instead of 'device name', there seems to be a precedent in
/usr/share/man/man1
Prompted By: bde
|
| |
|
|
|
|
| |
'devicename'.
|
|
|
|
| |
2. Back up old rc.conf.site if it exists.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Submitted by: dfr
|
|
|
|
|
| |
PR: docs/9660
Submitted by: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
|
|
|
|
|
| |
know what revision of FreeBSD is being run. This case should never happen,
but just in case.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
PR: docs/9602
Submitted by: Kazuo Horikawa <horikawa@jp.freebsd.org>
|