Age | Commit message (Collapse) | Author |
|
of uninitialised memory in the sent icmp echorequest.
Reported by Adarsh Dinesh (adarsh.dinesh at gmail com)
OK florian@ deraadt@
|
|
it's invoked with either -A/-C/-L, which at the time I left alone due to some
forbidden ioctls by pledge(2).
Now we have unveil(2) and this path can be further restricted by using it
instead of chroot(2) since this "sandbox" (not sure why people call sandbox to
about everything these days) can be escaped with *at(2) calls.
Since no filesystem access is needed here then we can disable its access by
calling unveil("/", "") unveil(NULL, NULL).
added /* no filesystem visibility */ as per suggestion by and OK deraadt@
|
|
Brings various dhcp related daemons into line with
the common idiom.
ok florian@
|
|
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
OK deraadt@ jca@
|
|
human readable list of strings.
Slightly tweaked version of a diff from William Ahern via tech@.
Long silence on all fronts leads to community based testing.
|
|
dhclient(8).
|
|
|
|
domain-search. Mention that dhcpd(8) still calls
this option-119. Also mention that the information
provided by this option will be used in preference
to domain-name when constructing resolv.conf(5).
Merciless prodding by florian@ and kn@.
|
|
classless[-ms]-static-routes verbiage to use
cidr and ip-address types rather than hand
waving manual construction.
Add an explicit note that dhclient(8)
ignores the obsolete "static-routes"
option.
|
|
mention them.
|
|
dhcp-max-message-size (a.k.a. option 57) in the hope of clarifying
things.
|
|
nds-context and nds-tree-name to show that they
are parsed as data-string ('X') and not string ('t').
Correct the documentation of dhcp-option-overload to
show that it is parsed as a single uint8, not an
array of uint8s.
|
|
BIOCSFILDROP used to just be a flag, ie, any non-zero value was
treated the same, but i'm changing it so different values do different
things. this way the programs should keep working even if i decide
to change the values for these macros.
|
|
looked at the error handling here, and.... oh my.
If opening /dev/pf on startup fails, don't just warn and move on, but bail.
If chroot (or the chdir after) fail, don't just warn and move on, bail.
If dropping privileges fails, the last thing we want to do is to just move
on with root privs, having warned or not.
If the pipe to the parent process is closed, that almost certainly means
that the parent process went away, and it absolutely certainly means that
the table handler process has no meaningful reason to exist any more, thus
bail.
ok florian ccardenas krw
|
|
to make it clearer. Explicitly mention that older
printers may require it to be set to false, as this
has come up on the mailing lists a few times.
Original diff from sthen@.
ok jmc@
|
|
note that this is only part of raf's original diff: the rest is for
code. although i'm sure the diff itself is correct, i don;t judge
myself qualified to decide whether those changes are warranted.
still, i'd appreciate at least a reply to raf's diff from another
developer (yay! nay!)
|
|
ok krw@, tweaks by jmc@
|
|
issue pointed out by miod
ok krw miod
|
|
|
|
|
|
The dhcpinform() function has assumed that ciaddr matches the packet's
IP source address and didn't consider a relay, such as dhcrelay(8) -
indicated by giaddr, has forwarded the request.
Tested by landry@
OK krw@
|
|
hostnames which resolve to muliple ip addresses are all forwarded to
the client;
issue reported by edgar pettijohn;
discussed with dhcpd's de facto maintainer, kenneth westerback;
|
|
|
|
|
|
turned off for those clients and networks that find it impossible to
move past RFC 2131. Modelled on the same statement in recent ISC
versions, though we default to 'on' (a.k.a. RFC 6842) rather that
'off' (a.k.a. RFC 2131).
Problems reported by Bastien Durel (Xerox Phaser 6022 printer) and
Bryan Vyhmeister (Hon Hai Precision router) via misc@. Thanks!
|
|
around for two releases, it should be safe to do so.
ok bluhm deraadt sthen tb yasuoka
|
|
sanity improvements reyk@ recently put into dhcrelay to ensure no more than
the captured packet is processed.
|
|
had it correct. Don't BPF_WORDALIGN() the value for the number of
bytes read() into the buffer. This could theoretically cause the
processing of 1 - 3 more bytes than were read.
|
|
dhclient. Eliminate extra prototypes for checksum() and wrapsum().
|
|
and enums.
|
|
|
|
|
|
its friends.
|
|
warn with the same severity. Switch log_warn() to LOG_ERR and keep
fatal() at LOG_CRIT.
OK reyk@ florian@
|
|
placement logic from dhclient.
|
|
Point out that dhcpd(8) -f is an alias for -d.
|
|
log_warn(). Zap a couple of explicit 'syslog()' calls.
|
|
|
|
fatalx() -> fatal() and even a couple of fprintf(stderr) -> log_warn().
|
|
|
|
ok benno@
|
|
with standard daemon log.[ch].
ok mpi@
|
|
tb@ was initially concerned about next-server but there were more
similar occurrences. Simple solution - "hostname" - proposed by jmc@
ok from both
|
|
"Looks good" to deraadt@
|
|
value specified in dhcpd.conf.
i.e. don't assume it is always the primary address of the interface
the packet arrived on.
Fixes issues with redundant dhcpd servers and CARP'd interfaces.
Issue reported and fix tested by Johan Huldtgren
|
|
- Use explicit_bzero(3) instead of bzero(3) to clean temporary HMAC
OK krw@
|
|
inappropriate. Which is why client_identifier_len exists.
Replace copy&pasted strlen() with client_identifier_len.
Symptoms (crash) and cause (bad c&p) spotted by sthen@.
tested & ok sthen@
|
|
RFC 3042 says servers that do not understand the option will not
echo it.
Plus, our desultory attempt at echoing was almost certainly broken
for OFFERs (use after free of packet data) and not even attempted
for NACKs.
ok millert@
|
|
the client-identifier value. RFC 6842 says the server MUST echo it.
Echoing the information disambiguates packets for relays and clients
when chaddr is 0. Similar to what dhcpv6 does.
|