Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Friendly reminder from anton@
|
|
|
|
worked out what was missing
- remove commented out entry to non-existent en(4) driver
- remove all instances of .Tn
ok miod dlg
|
|
The RTL8192EU is up to two stream TX/RX (so MCS0->15).
ok stsp@
|
|
|
|
|
|
From Dmytro Laktyushkin
4ac57c3fe2c0a74c6239170fc58fc824637c6015 in linux-6.1.y/6.1.26
6d9240c46f7419aa3210353b5f52cc63da5a6440 in mainline linux
|
|
From Alan Liu
bef774effb278ff0b65ea2dbaa1ab32ba6a1dc13 in linux-6.1.y/6.1.26
c8b5a95b570949536a2b75cd8fc4f1de0bc60629 in mainline linux
|
|
From Ville Syrjala
66eb772be27e228716bb81feee0400d995cbe605 in linux-6.1.y/6.1.26
e1c71f8f918047ce822dc19b42ab1261ed259fd1 in mainline linux
|
|
From David Gow
fb766acce3cf1c9637a79c1ffb3cebc61fd9d859 in linux-6.1.y/6.1.26
4453545b5b4c3eff941f69a5530f916d899db025 in mainline linux
|
|
Chosing [W]hole on a GPT disk means it needs non-default `-b' fdisk(8)
to boot and preserve any existing BIOS boot partition.
With 'Encrypt the root disk?' answered postively, the crypto disk instead of
the root disk becomes the boot disk.
Extend the sanity check to both crypto and root disk, really asking
"is this a boot disk?".
This preserves existing boot partitions when using guided disk encryption.
|
|
Chosing an existing OpenBSD partition on GPT during disk setup requires an
existing EFI Sys partition (the installer does not create it in thi case).
With 'Encrypt the root disk?' answered postively, the crypto disk instead of
the root disk becomes the boot disk.
Extend the EFI Sys sanity check to both crypto and root disk, really asking
"is this a boot disk?".
|
|
|
|
table variations (calculate address into %rax, jmp %rax) which is not
compatible with IBT endbr64. The specific generated code sequence was
found inside clang, which made the debugging experience pretty miserable.
So we will have to disable jump tables by default.
ok kettenis
|
|
ok beck
|
|
The program won't exit with a non-zero exit code if X509_CRL_set_*
tests fail, as the relevant bits haven't been committed to libcrypto yet.
|
|
This is intended to be able to test rpki-client in a reproducable
way without worrying about the system time changing the results
ok claudio@
|
|
-fcf-protection=branch is the default). All binaries grow slightly, but
we can slowly move towards greater IBT enforcement in userland.
4th or 5th variation of this diff, with mortimer
ok kettenis
|
|
property name instead of "phys".
ok dlg@
|
|
ok beck
|
|
|
|
|
|
|
|
|
|
values for the block/fragment sizes that some install media need.
Hoist the desired values into the newfs(8) invocations to make it
obvious non-default values are required and what the values are.
No functional change.
|
|
|
|
and return -1 in json_do_finish().
tb@ thinks this is not to horrible
|
|
|
|
This used to be public API but is now only used for debug code that has
certainly never been used since it was released to the public. It drags
that debug nonsense with it.
ok beck
|
|
time kernel and net locks are held in various combination to protect it.
We don't want to put kernel lock to all the places. Netlock also can't
be used because rtfree(9) which calls rtlabel_unref() has unknown
netlock state within.
This new `rtlabel_mtx' mutex(9) protects `rt_labels' list and `label'
entry dereference. Since we don't export 'rt_label' structure, keep this
lock private to net/route.c. For this reason rtlabel_id2name() now
copies label string to externally passed buffer instead of returning
address of `rt_labels' list data. This is the way which rtlabel_id2sa()
already works.
ok bluhm@
|
|
ok tb@ jsing@
|
|
OK tb@
|
|
|
|
The old policy codes remains the default, with the new policy code
selectable by defining LIBRESSL_HAS_POLICY_DAG.
ok tb@ jsing@
|
|
We add this locally as a function to avoid delving into
the unholy macro madness of STACK_OF(3).
ok tb@ jsing@
|
|
OK tb@
|
|
ok tb@ jsing@
|
|
ok tb@ jsing@
|
|
ok tb@ jsing@
|
|
ok tb@ jsing@
|
|
|
|
This is an implementation of the X509 policy processing using a
DAG instead of a tree to avoid the problem of exponential expansion
of the policy tree as specified in RFC 5280
For details see:
https://boringssl-review.googlesource.com/c/boringssl/+/55762
ok tb@ jsing@
|
|
to start working on it in the tree.
|
|
applicable provider
Reported by Ties de Kock
OK claudio@
|
|
|
|
Needed for bison.
|
|
|