| Age | Commit message (Collapse) | Author |
|---|
|
don't need check cmd twice.
ok miod@
|
|
|
|
|
|
|
|
|
|
|
|
implementation.
ok miod@
|
|
multiple routing tables. Currently it doesn't do anything useful
but it's a prerequisite for any future work in this direction.
ok sthen, reyk, blambert
|
|
Amling.
|
|
|
|
deletion via the dead_key_bindings tree. From Keith Amling.
|
|
|
|
verbiage;
ok millert
|
|
fsck_ffs stopped providing it.
|
|
simply say all other combinations are behaviour undefined;
ok guenther, who reminded me to change these too;
|
|
- document undefined behaviour for unlisted formats in
combination with `#'; guenther helped me organise this into a saner
piece of text
ok guenther
|
|
in the case where the rdomain was not switched. Make sure ifa_add() is
only called if ifa_del() was called previously. Hopefully we got all the
corruption fixed.
With and OK mpi@
|
|
|
|
|
|
|
|
|
|
DEV_BSIZE. David Vasek says it still works the same on 4K-byte-sector
device. i.e. prints one value incorrectly. For which a fix should
be following soon.
|
|
fix null deref spotted by Seth Hanford, pinpointed by dtucker@
ok florian@
|
|
receiving pointer -> index conversion. No functional change.
ok claudio@, mikeb@, lteo@
|
|
split-window, respawn-window or respawn-pane, pass them directly to
execvp() to help avoid quoting problems. One argument still goes to "sh
-c" like before. Requested by many over the years. Patch from J Raynor.
|
|
|
|
much as before - buffers are automatically named "buffer0000",
"buffer0001" and so on and ordered as a stack. Buffers can be named
explicitly when creating ("loadb -b foo" etc) or renamed ("setb -b
buffer0000 -n foo"). If buffers are named explicitly, they are not
deleted when buffer-limit is reached. Diff from J Raynor.
|
|
Grow the array of cached inodes exponentially instead of arithmetically.
Prefer sizeof(*pointer) over sizeof(type) in mallocs.
Don't leak memory in searchdir().
Fix multiple bugs in the handling of indirect blocks, including reuse of
a static buffer in a recursive function and failure to track the remaining
size of the directory blocks to process
Tested with a directory *doubly* indirect block!
ok krw@
|
|
function when SMALL is not defined. OK guenther@
|
|
for client/server processes checks through $self->{down} state control
variable, while here, do not instantiate a client when noclient is defined,
reflecting server object instantiation behaviour.
ok bluhm
|
|
sblock_try[] entries by DEV_BSIZE to get proper 512-byte-block address
for bread().
Confirmed to still work on 4k-byte sector devices by David Vasek.
|
|
probably more 32-bit platforms).
Problem noticed by tobiasu@; ok tobiasu@ dtucker@ sthen@ benno@
|
|
it possible to use the non-mappable part of the GTT, prepares the way for
using the PPGTT and reduces the diffs with Linux.
ok jsg@
|
|
|
|
|
|
two keys and four IVs to do much magic, is specified as such with test vectors,
but the implementation actually always uses the first key, and the test vectors
were computed with it, so they are wrong.
Fixing the code to match the intended specification would break
interoperability with existing code (assuming such code would exist), so it is
better to remove this interface, which is obviously too complex for mere
mortals if even its author can not implement it correctly.
Riding on the libcrypto major bump.
|
|
|
|
ASN1_unpack_string() from the NO_ASN1_OLD purge; turns out that some Ruby
extensions still use them, unfortunately, so we need to give them some more
time to catch up on ``recent'' interfaces.
Riding on the libcrypto major bump.
|
|
of 64-bit data, and only used by DTLS, to libssl where it belongs.
Remove pqueue_print() which is a debugging interface and serves no useful
purpose, except for the regress test, which grows its own pqueue_print()
routine.
Bump libcrypto major and libssl minor.
WARNING: do not update your tree right now, more changes are coming, which
will ride the libcrypto major bump.
|
|
|
|
while changing things, add a crypt_checkpass wrapper that handles most of
the edge cases. (not quite ready for production, though.)
ok deraadt
|
|
fix potential integer overflows in memory allocation (mostly for pedagogical
purposes, these are unlikely to overflow in practice)
move the rest of lst.lib stuff into its own directory.
|
|
It's not a standard interface, so it doesn't belong in libc.
I hate duplicating the code in client programs, so do beck@, kettenis@,
schwarze@, millert@, miod@... and they agree with libutil.
|
|
(mostly use a calloc function to avoid potential integer overflow)
|
|
deterministic behavior. four selected because it's more than three, less
than five. i.e., no particular reason.
|
|
that lack the appropriate address info.
Simply ignore the message as is done for short or incorrectly
versioned messages
ok claudio@
|
|
a backport from FreeBSD's r205728, r224511 and 225839 without the new
functions to set/get a report ID nor the usbhidctl(1) & usbhidaction(1)
bits.
Committing now to open the "Monday's Bump Parade".
|
|
infrastructure.
The following tests have not been imported, for their code lacks a licence:
asn1, rsa, sha256, sha512, wp.
|
|
the server.
ok gilles@
|
|
|
