Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
described in
648364-001 Intel 600 Series Chipset Family Platform Controller Hub Datasheet
655258-001 12th Generation Intel Core Processors Datasheet
|
|
timeout.
|
|
partition 0 information from the default MBR.
loongson and macppc provide partition 0 information but no boot code.
amd64, i386, landisk provide boot code but no partition 0 information.
Other arch's get by w/o a default MBR (a.k.a. /usr/mdec/mbr).
No functional change.
|
|
|
|
out of date: remove it (sthen) and add a pointer to -C (dlg);
ok sthen
|
|
mask failed kqueue_register() attempts which in turn causes the thread to
end up sleeping as opposed of propagating the failure to user space.
Regression introduced in the recent switch to implement poll on top of
kqueue.
Thanks to Larry Hynes <larry at larryhynes dot com> for reporting and
Leah Neukirchen <leah at vuxu dot org> for providing a reproducer; which
also already made its way into regress.
ok mpi@
|
|
between 1-255 where 0 is reserved. The pseudo report ID
UHIDEV_CLAIM_MULTIPLE_REPORTID is currently colliding with the valid
report ID 255. Therefore crank it which gets rid of the collision and
increase the related fields in order to cope with larger integers.
Thanks to Damien Couderc <openbsd at petrocore dot eu> for reporting and
testing.
|
|
to fail if parsing of a certificate extension failed.
Adjust the documentation accordingly.
OK tb@
|
|
tested by robert@ on PL2303GT
ok deraadt@ robert@ patrick@
|
|
|
|
ok deraadt@ robert@ patrick@
|
|
Fixes panics caused by attempts to grab audio_lock twice in the
interrupt code path: once in the low-lever interrupt handler and once
in selwakeup()
This is exactly how audio(4) handles this problem.
ok mpi
|
|
|
|
poll(2) rewrite on top of kqueue is currently blocking instead of
returning. Regression reported by Larry Hynes with a reproducer
from Leah Neukirchen, thanks a lot!
|
|
indicates failure. The previous "error return" X509_V_ERR_UNSPECIFIED
translates to 1, i.e., success. This changes to the intended behavior
of x509_purp.c r1.3 and matches OpenSSL. This will need various
adjustments in the documentation.
ok jsing
|
|
|
|
from Emil Engler
|
|
|
|
while here, add the missing const qualifier to the obj argument of
X509_EXTENSION_create_by_OBJ(3) and correct a typo in the argument
name of X509_EXTENSION_get_data(3)
|
|
also documenting X509_REQ_print(3) and X509_REQ_print_fp(3)
|
|
as the notification file.
OK tb@ job@
|
|
check of the content-lenght header and also with a check when writing
data out so that chunked encoding can not bypass the limit.
OK beck@ job@
|
|
This uses scan_scaled(3) from libutil which is very similar to how rsync
behaves. Not implemented are the +/-1 math and the 1000 vs 1024 multipliers.
OK benno@ job@
|
|
From Fabian Stelzer
|
|
- adds generic find-principals tests (this command had none before)
- tests certs with a timeboxed validity both with and without a
restriced lifetime for the CA
- test for a revoked CA cert
by Fabian Stelzer
|
|
|
|
With and OK tb@
|
|
and that is where we want it to be, GitHub issue 2956.
|
|
|
|
|
|
|
|
is meant by "independently of the host network stack"
feedback jmc dlg
|
|
|
|
OK claudio@
|
|
OK claudio@
|
|
|
|
|
|
rpki-client wants --max-size and this will unblock that work.
With job@
|
|
|
|
MAX_FILE_SIZE after base64 decoding it. This way hostile RRDP servers
do less damage.
OK beck@ tb@
|
|
|
|
|
|
This is not yet hooked up and will not compile. Follow on commits
will KNF and then make it build.
ok jsing@ tb@
|
|
ruby can no longer generate certs with bogus wildcards in it to check
that they will fail to verify when creating TLS connections. It will
throw an error. This change needs openssl-ruby-tests-20211024p0 or later
to work.
|
|
Original commit message from beck:
Validate Subject Alternate Names when they are being added to certificates.
With this change we will reject adding SAN DNS, EMAIL, and IP addresses
that are malformed at certificate creation time.
ok jsing@ tb@
|
|
There is no requirement other than replying to client port 68/udp
as per RFC 2131, so drop the 67/udp check.
Same conclusion from florian
Reported and tested by Roc Vallès < vallesroc AT gmail DOT com>, thanks!
|
|
In most cases we already warn and continue if someone sends us malformed
x509 objects. This makes this consistent behaviour in all places
so that if someone passes in bogus X509, We end up failing their entry
and continuing rather than exiting.
We still exit on memory/system failures so that a future run of rpki
client can simply do better when the machine is perhaps less hammered
on
ok job@ claudio@
|