| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
check the cksums of the attribute values instead of comparing the
revisions. diff from NetBSD through naito.yuichiro at gmail.com. test
by kolipe.c at exoticsilicon.com.
ok kevlo miod deraadt
|
|
|
|
dropping the empty RETURN VALUES section
and adding the missing "#include <stdilib.h>" below EXAMPLES.
|
|
rename the "ev" argument to "event" to make some text read better,
and get rid of colons at the ends of list tags.
OK jmc@ and Ted Bullock.
|
|
that provide type-specific functionality here.
While here, fix some wrong return types in the SYNOPSIS.
|
|
that provide type-specific functionality here,
and add the missing return type to one function prototype.
|
|
unconfigured during boot, now that timer(4) is gone.
|
|
in the manual pages of the respective BIO types.
|
|
in the manual pages of the respective BIO type.
While here, fix some wrong return types in the SYNOPSIS.
|
|
Same logic and argument as for the parent *S ioctl unlocked in r1.400,
might as well have committed them together:
Both ticket and number of queues stem from the pf_queues_active list which
is effectively static to pf_ioctl.c and fully protected by the pf lock.
OK sashan
|
|
ok deraadt
|
|
|
|
produce a spurious error (so 1 chance in 2^26)
It's like read/write: we need to recognize 0 as EOF and not try to checksum
a non-existing block.
while there, also make sure that we got all the signed blocks at EOF
before exit(0)
Note that none of those two bugs affect the actual security of signed
packages: the basic assertion that only signed data gets written
through the pipe is still 100% valid !
but it's a good idea to not emit spurious messages for valid files, and also
to recognize truncated files !
okay tb@ (thanks a lot)
|
|
ok mlarkin@, patrick@
|
|
the --rsync-path option. So we can see whether the tests pass in
all interoperability combinations.
Suggested by claudio@
|
|
This tells gcc that OPENSSL_assert() will not return and thus avoids a
silly warning that triggers scary gentoo QA warnings.
From claudio
|
|
Previous change to allow overriding changed the way we parsed and
stored the boot image path. The lifetime of the path was...much too
short. Heap allocate the kernel path.
Found by Mischa Peters.
ok mlarkin@
|
|
|
|
|
|
confusing warning messages complaining about macros that don't even
appear in the input file.
As a welcome side effect, this also shortens the code...
Fixing a minibug
reported by Alejandro Colomar <alx dot manpages at gmail dot com>.
|
|
|
|
ok bluhm@
|
|
vmd allows non-root users to "own" a vm defined in vm.conf(5). While
the user can start/stop the vm, if they break their filesystem they
have no means of booting recovery media like a ramdisk kernel.
This change opens the provided boot kernel via vmctl and passes the
file descriptor through the control channel to vmd. The next boot
of the vm will use the provided file descriptor as boot kernel/bios.
Subsequent boots (e.g. a reboot) will return to using behavior
defined in vm.conf or the default bios image.
ok mlarkin@
|
|
failing test so that claudio@ can fix them.
|
|
No functional change. virtio block/networking emulation do not need
to know about vmm or any kernel types.
|
|
discussed with kettenis@, ok deraadt@
|
|
Found with the help of Otto's malloc memory leak detector!
|
|
|
|
The timer(4/sparc64) driver was effectively disabled during the
previous release. Nobody has come forward asking for it to be adapted
to work with the new clockintr framework, so it's time to remove the
driver from the tree.
As of today, if you want to run OpenBSD on SPARC v9 hardware, that
hardware needs to sport either %tick and %tick_compare (%asr23), or
%stick (%asr24) and %stick_compare (%asr25).
All Sun/Oracle SPARC v9 hardware meets these conditions, from the
UltraSPARC I onward.
Most HAL/Fujitsu SPARC v9 hardware meets these conditions, from the
SPARC64 III onward. The only HAL/Fujitsu hardware that might not have
%tick_compare are the HAL SPARC64 I and SPARC64 II, for which I can
find no documentation. However, those processors are currently
unsupported by OpenBSD for other reasons, so their support status is
unchanged by the removal of this driver.
With help from miod@.
Link: https://marc.info/?l=openbsd-tech&m=167898759928206&w=2
"after unlock" deraadt@, ok mlarkin@ miod@
|
|
debugged with job
|
|
(which they aren't), so appease them.
|
|
installboot'ing due to incorrect d_type (must be 'floppy' not
'vnd') in disklabel.
Noticed by deraadt@ and sthen@
|
|
A long time ago a workflow was envisioned for X509, X509_CRL, and X509_REQ
structures in which only fields modified after deserialization would need to
be re-encoded upon serialization.
Unfortunately, over the years, authors would sometimes forget to add code in
setter functions to trigger invalidation of previously cached DER encodings.
The presence of stale versions of structures can lead to very hard-to-debug
issues and cause immense sorrow.
Fully removing the concept of caching DER encodings ensures stale versions
of structures can never rear their ugly heads again.
OK tb@ jsing@
|
|
While here, also correct the HISTORY section.
OK jmc@
|
|
as intentionally undocumented. Do that here because no related
manual pages exist.
|
|
This ensures that we will no longer silently ignore a certificate with
a critical policy extention by default.
ok tb@
|
|
undocumented because they are NOOPs or deprecated.
|
|
|
|
with beck
|
|
improve it in tree.
|
|
|
|
It can go play in the fields with all the other exponential time policy
"code".
discussed with jsing
ok & commit message beck
|
|
Correct the return types of some macros.
Improve the RETURN VALUES section.
|
|
|
|
ok beck jsing
|
|
Tell it we deliberately ignore the return value, (we really don't
care what the old comparison function was).
|
|
"Failure to re-encode on modification is a bug not a feature."
OK jsing@
|
