The problem here is setuid(euid) is used far too much. Since I removed
many of these calls, and added no new ones, I do not think this weakens
security. In fact, it quite likely improves it quite a bit, since
access() is called as the real userid, and the file is opened for printing
as the real userid rather than the (setuid-root) effective one.
map. SunOS ypservers maps place the host name in the key and the val,
but HP-UX and NetBSD ypservers maps place the hostname only in the
key, leaving the val empty. Since there is no clear standard for this map,
best to play it safe.
there are some PC/Mac oriented devices that use non-standard speeds,
furthermore that's just not the way we do things anymore.
"Bad" baud rates are no longer caught with their own error message,
but the condition will still be diagnosed when the tcsetattr() fails.
- check malloc returns
- null terminate strncpy() strings
- use snprintf instead of sprintf
- pass the right arguments to the right functions
- check usage
- use err(3) and warn(3) instead of printfs.
Correct length arg to haddrtoa() in report of duplicate address.
The string value for a generic tag should not include the null.
(Including the null in reponses really annoys HP printers!)
When reading hardware addresses, allow colon separators
(only works if the whole H/W address is in quotes).
Also, change `.Os 4.2' => `.Os 4.4' (this man page is from 4.4 lite), and
for now, refer to the "BSD 4.3 Line printer manual", because that is what
we now have in lpr/SMM.doc (SMM.doc needs updating too).
believe that's been missing for so long!)
While I'm here, remove all of the non-hp300 cruft. The hp300 port is the
only thing that uses config.old(8) now'a'days. Yes, this is a little
embarassing.
by Mike Grupenhoff <kashmir@umiacs.umd.edu> in PR #2485.
While I'm here, do some long-overdue cleanup, including function prototypes,
and update for modern libkvm interfaces.
ypbind; sleep 10; ypwhich
to fail (where failure is defined as ypwhich hangs until it gives up,
complaining about not being able to communicate with ypbind). Failure
mode pointed out by Chris G. Demetriou <cgd@cs.cmu.edu>.