| Age | Commit message (Collapse) | Author |
|---|
|
capability is enabled, not when annoucing the refresh capability is
enabled...
Alex Hunsaker <badalex@gmail.com> ran into that issue
|
|
an ip address, that's for sure; pr 5232 arjones@simultan.dyndns.org
|
|
Namely:
- anything that doesn't belong to owner root/bin, group bin/wheel
must be annotated in the packing-list.
- any file setuid, setgid, writable by others must be annotated in
the packing-list.
These warnings must be fixed. They will become errors in the near futur.
|
|
being a new tool. My bad.
prompted by deraadt.
|
|
|
|
does not dump all relevant tables and will eventually be deprecated by this.
It needs some more cleanup but we need to start getting acpi dumps from
the field using this instead of acpidump.
Code written by jordan, cleanup by me.
ok jordan@
|
|
INADDR_ANY. Spotted out by Martin Boehme.
OK claudio@ henning@
|
|
negative index array access.
OK moritz@.
|
|
found by Martin Boehme. ok michele@
|
|
Spotted by janus <at> errornet.de
|
|
received
|
|
Modulate the timer with an MD5 hash of the key to generate the sequence number.
Ensure that the most significant bit of the modulated value is 0 to prevent
wrapping of the sequence number.
ok michele@
|
|
Convert a strncpy() to strlcpy() since it is followed by strlcat().
OK marco@ mk@
|
|
from Makefile. ok millert@
|
|
This allows construct like these:
area 0.0.0.1 {
interface lo0
interface em1 { passive }
}
From Pierre-Yves Ritschard
|
|
ok claudio@ deraadt@
|
|
time, and make ntpd use that to send the next uery to an ntp peer and the
like. this has the advantage that changes to the clock do not interfere
with the intervals. for example, when we start on machines without an
RTC and the initial settime (-s) kicks in, intervals were strange.
idea from amandal@entrisphere.com, this implementation by me
tested ckuethe, phessler, mbalmer, ok mbalmer
|
|
* remove SAs and flows later again, even if the
* configuration info changed due to reload.
* We need: SPIs, method, local_addr, remote_addr.
* remote_addr cannot change, so no copy.
with this, I have just migrated a session from tcp md5sig to ipsec esp ike,
just with bgpctl reload (both sides) followed by bgpctl neighbor $foo clear
(just one side)!
claudio ok
|
|
is not such a good idea - it gets nulled on config reloads, and thus
we fail to clear the old SAs when the session is restarted after a config
reload occured. obvious solution: store the SPIs outside the config area.
ok claudio
|
|
|
|
Pierre-Yves Ritschard <pyr@spootnik.org>
|
|
|
|
somewhere else?
|
|
|
|
bgpd (2004 :)), and spread ;(
|
|
|
|
From Pierre-Yves Ritschard
|
|
possible integer truncation because of the use of u_longs and u_int32_t in
the code. Initial diff by Pierre-Yves Ritschard but slightly modified version
commited.
|
|
|
|
|
|
them only every 30 seconds. now query them every 5,and take the median
value from 7 queries as sensor value. this takes outliers out of the
equation and makes the overall result much better, especially for
sensors with heavy jitter (like nmea for now)
|
|
OK cloder@.
|
|
now that it is the default;
ok henning mcbride camield (ftp-proxy bits) deraadt
|
|
|
|
From: amandal@entrisphere.com
|
|
-1 because of error, it may still participate in poll()
causing poll() to repeatedly wake up on error fd.
so make sure w edon't add -1 fds to pollevents to avoid unnecessary wakeups
From: amandal@entrisphere.com
|
|
From: amandal@entrisphere.com
|
|
too. from amandal@entrisphere.com
|
|
|
|
|
|
|
|
|
|
ok bernd, espie
|
|
All relevant information in the rip daemon can be displayed with this
controller.
Not connected to builds yet.
ok claudio@
|
|
imsg/three process framework of ospfd. He implemented most of the daemon with a little help and guidance from Claudio and I. Currently the daemon is more or less complete, with the exception of key lifetime and rollover. Not yet connected to the builds. OK claudio@
|
|
started by Michele Marchetto some time ago by using the imsg/three process framework
of ospfd. He implemented most of the daemon with a little help and guidance from
Claudio and I.
Currently the daemon is more or less complete, with the exception of key lifetime
and rollover.
Not yet connected to the builds.
OK claudio@
|
|
|
|
provided nothing else happens (like, huh, the presence of actual conflicts
between files).
Allows nikolay@ to work with redhat/base and fedora_core at the same time.
|
|
otherwise.
|
|
|
