| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Clean up some of the media handling to use common routines.
|
| |
|
|
|
|
| |
Better screen saver descriptions.
|
| |
|
| |
|
|
|
|
| |
Submitted by: Kevin Street <street@iname.com
|
| |
|
|
|
|
|
|
| |
Change unit to device access in lptcontrol.c. Now usage is
lptcontrol -i | -p | -e [-d /dev/lpt?]
|
|
|
|
|
| |
Mention more rfc numbers.
Don't ``.Nm Ppp'' (just use ``.Nm'').
|
| |
|
| |
|
|
|
|
|
| |
Obtained from: PAO3
Reviewed by: -current list
|
|
|
|
|
| |
PR: 10044
Submitted by: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
|
| |
|
| |
|
|
|
|
| |
script, expand words in the same way as !bg does.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
incorrect; returning NULL here means that the dispatcher won't send any
response back to the caller, which means the caller will sit there waiting
until it times out. I don't know how this ever worked before. The effect
is that using 'ypset foo' to get the local ypbind to change servers would
work, but would sit there hanging for a long time for no reason.
|
|
|
|
|
|
|
|
|
|
|
| |
Under certain conditions (possibly associated with heavy load), ypserv will
fork() child processes that don't exit like they're supposed to. I think
this is because of some suspect logic in the ypproc_all procedure. I updated
it to use what I hope is a more bulletproof approach.
Also tweaked yp_svc_run() a little so that the 'are we a child?' test happens
at every pass through the for(;;) loop, not just immediately after returning
from svc_getreqset2().
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|