Age | Commit message (Collapse) | Author |
|
modified inside signal handlers. Instead of returning a function
pointer, the state functions now return an enum for the next state.
This is used as an index into an array of function pointers to
do the actual state change in transition(). OK deraadt@
|
|
ok mikeb
|
|
|
|
containing the MBR template. Most especially don't get upset when
the 512-byte file does not contain a full 4096 byte disk sector.
Allows 4096-byte disks to be fdisk'ed once more.
Problem reported and fix tested by Gerald Hanuer via bugs@.
ok deraadt@
|
|
(e.g. the policy might be used-after-free on 'ikectl reconfig')
ok mikeb@
|
|
Reported by trondd at kagu-tsuchi ! com, thanks!
|
|
|
|
Tweak pfctl to respect the rule ID parameter (-R) specified
along with the show states (-s states) option to filter out
states that are not associated with a given rule from the
output.
ok sthen, benno
|
|
Pointed out by Markus Elfring
OK mikeb@ millert@
|
|
With help and ok from mikeb@
|
|
is non-portable. Also add missing asprintf() return value checks.
OK deraadt@ guenther@ doug@
|
|
|
|
from Benjamin Baier
|
|
|
|
mfi(4). Based on FreeBSD, but done without mfiutil(8).
OK deraadt@
|
|
|
|
|
|
Based on diff from Manuel Giraud (manuel (at) ledu-giraud.fr) Thanks!
|
|
|
|
Reported long ago by matthieu@. Also Jacob Berkman via the lists.
Tests and suggestions from Jacob and Matthieu.
|
|
present. The latest routing stack code can now handle these situations.
Much requested by beck@ and others. Detailed discussion at s2k15
identified required routing changes.
ok claudio@
|
|
|
|
example)
ok florian jsing
|
|
after modifying them. Give this flag to `display.focus', since screen
switching is asynchronous, and reading back will return the screen we are
switching from if the switch has not completed yet.
Also, disallow -= and += syntax for display.focus, as it doesn't make any sense.
|
|
the changes for handling template files in r1.293, alloc_table became
a pointer to an array of structs (rather than the array itself), so
nitems(alloc_table) no longer returns the number of elements. As found
by sebastia@, autosize would only try the first allocation scheme,
so installation would fail on small disks. ok henning@
|
|
|
|
Correct old style entries so nothing has to be done for the admin.
diff from Manuel Giraud (manuel (at) ledu-giraud.fr) Thanks!
|
|
Pointed out by bluhm@; no object change.
OK bluhm@, krw@
|
|
No object change.
|
|
Input bluhm@, OK krw@
|
|
in get_token(). Simplifies code and shrinks future diff.
No intentional functional change.
|
|
encountering a carriage return in the input.
Found by jsg@ a long time ago in a respository far, far away.
|
|
or take a cast. Tweak error messages to also be consistant with
ping(8).
Change lower bound of '-h' to 0 from -1 at the request of florian@.
Tweaks and suggestions from, ok florian@
|
|
|
|
|
|
template gives mountpoints, min-max size ranges and percentage of disk
foremost intended for autoinstalls, installer bits to follow soon.
with input from many, ok theo
|
|
missed one. This diff is only a spacing change.
|
|
that for us.
approach seems sound deraadt@
ok claudio@ mpi@ henning@ phessler@
|
|
ok deraadt@
|
|
|
|
ok henning
|
|
a fstat() call.
ok mikeb@ markus@
|
|
to the same policy is already active. OK markus, hshoexer
|
|
> add a mac to the timestamp payload and calculate it with siphash.
>
> this lets us have some confidence that the timestamp hasnt been
> damaged or tampered with in transit.
>
> discussed with jp aumasson
> ok florian@
|
|
i dont know why i missed this before.
|
|
an unvarying payload.
each ping process generates a random key, and each packet then uses
the timestamps mac as the IV for the stream.
this allows us to have a different payload per packet that we can
recalculate and compare in the same was as the static payload was
checked before. by aggressively varying the payload we hope to
generate more opportunities for dodgy network equipment to show
errors.
note that we do siphash before chacha because we want to be strict
about the timestamp payload, but we want to be able to recognise
errors in the rest of the payload and where those errors were. doing
chacha before siphash would have us than fail the whole packet if
a checksum doesnt match.
discussed with jp aumasson
ok florian@
|
|
this lets us have some confidence that the timestamp hasnt been
damaged or tampered with in transit.
discussed with jp aumasson
ok florian@
|
|
handling along the way.
Reviews by Brendan MacDonell, Jeremy Devenport, florian, doug, millert
|
|
|
|
ok krw@
|