acme-client: treat eab and eab_key as secrets
Wipe them with freezero after use and also make sure to delete possible
remnants of them on unbase64buf_url() failure.
reads fine to florian
ok jmatthew
test: prefix name with parent test
Add parent test's name as a prefix to subtests, in the format
"test-1/sub-test-1/sub-test-2".
This copies Go's format for subtest names, and makes it easier to track
where a test is running when using many nested subtests.
Also add input checks to ensure parent and name are not NULL for
subtests.
ok jsing
acme-client: zero optarg for external account binding
After copying the key-id:key pair, wipe the optarg so that this secret is
not visible to other users during the entire run time (in ps for example).
From Acts1631
reads fine to florian
ok jmatthew
printf(3/9): In the o conversion the # flag asks for a leading zero
Fix for Defect Report #151 in our libc.
https://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_151.html
Original diff from Showta Ishizaki.
ok asou@
also looks correct to me deraadt@
kubo/go-ipfs: update to 0.43.1 to fix build with go 1.27
Only compile tested. If anyone cares about this, it would be really nice
to have a maintainer that deals with this thing that breaks every half a
year due to the use of cockroachdb's swiss tables.
sdl3: use getexecpath(3) for SDL's GetExePath(). From Brad - thanks!
Leave XXX to remove obsolete and convoluted workarounds after
getexecpath(3) is universal.
Check signature of local SHA256.sig
We do this by improving the consistency of what we download vs the
file we trust for checksums and filenames.
This has the side effect of no longer writing and leaving an
unexpected SHA256 file with -F but does leave an invalid SHA256.sig
after error to be able to do diagnostics, as requested by sthen@.
While here, also tidy global variable setup for clarity.
Initially noticed by Acts1631 <acts1631kjv () proton ! me>
With much help and OK from dgl@
Correct botched size check in dtls1_preprocess_fragment().
Check message length against max, rather than fragment offset and length.
Due to a various questionable code, this allows for a crafted messsage
to be sent that results in a 21MB allocation, which then promptly results
in an error. Providing that the SSL context is cleared or freed, the
allocation then freed, meaning that this has minimal impact. A similar
fix was landed in OpenSSL in 48c054fec35, although this checks against
dtls1_max_handshake_message_len() rather than max.
Thanks to Abdullah Al Ishtiaq for flagging this.
ok kenjiro@ tb@
Work around smtiic(4) misbehavior to fix RTC setting & reboots
For some reason this i2c chip starts to misbehave after a few
hours/days, and when that happens setting the RTC or halting/rebooting
becomes impossible. Waiting a bit after enabling the device appears to
reliably fix this and alleviates the pain of handling remote machines
such as the riscv64.p ports cluster. There is probably a better fix but
I'm not sure which one exactly.
ok kettenis@
Reduce size of DTLS queues for unprocessed records and application data.
DTLS currently buffers records that contain handshake messages and alerts,
which are in the next epoch and cannot yet be processsed. This is done by
saving the entire buffer that is 16KB in size, regardless of the actual
bytes sent on the wire. With a queue limit of 100 it is possible to send a
small number of bytes on the wire and have the server allocate 1.6MB -
reducing the limit to 16 reduces the allocation to 256KB. This queue will
soon be removed entirely.
DTLS also currently buffers record content from application data where the
handshake has not yet finished. This only buffers the actual content
received on the wire and does not suffer from the same problem, however
reduce the queue size to further limit memory consumption.
ok kenjiro@ tb@
Introduce in-kernel 'shmid_ds_kern' structure where `shm_nattch' has the
type of uint64_t. The original 'shmid_ds' used to deliver data to the
userland, so API/ABI is not broken. The delivered `shm_nattch' value is
clamped with SHRT_MAX.
ok deraadt
