summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-03-06whack the *phy entries in SEE ALSO: it was becoming unwieldy, and they areJason McIntyre
already listed in SYNOPSIS; while here, rework the ifconfig sentence into something simpler, tweaked by jsg to mention the "media" keyword; ok jsg
2023-03-06syncTheo de Raadt
2023-03-06drm/amd/display: Properly reuse completion structureJonathan Gray
From Stylon Wang 118ad80d27d938868299ef184f7483b21f011f0b in linux-6.1.y/6.1.15 0cf8307adbc6beb5ff3b8a76afedc6e4e0b536a9 in mainline linux
2023-03-06drm/amd/display: Fix race condition in DPIA AUX transferJonathan Gray
From Stylon Wang 075e2099c32cf4486b27266d2aecf61e95499ea4 in linux-6.1.y/6.1.15 ead08b95fa50f40618c72b93a849c4ae30c9cd50 in mainline linux
2023-03-06drm/amd/display: Move DCN314 DOMAIN power control to DMCUBJonathan Gray
From Nicholas Kazlauskas 4da108082a3290804ebbd42d70ce8535c00e4637 in linux-6.1.y/6.1.15 e383b12709e32d6494c948422070c2464b637e44 in mainline linux
2023-03-05Fix clean process shutdown by storing env globally like vmd and httpd doTobias Heider
instead of getting it from p_ps. The old approach does not work anymore after the recent fork + exec update. ok patrick@
2023-03-05Actually, LANG only set the default.Antoine Jacoutot
from guenther@
2023-03-05Remove #ifndef OPENSSL_EC_NISTP_64_GCC_128.Joel Sing
This was presumably intended to be OPENSSL_NO_EC_NISTP_64_GCC_128, however generic code has ended up inside the ifdef (and none of the NISTP code or prototypes now remain).
2023-03-05arm64 needs -DBOOT_STTY as well.Mark Kettenis
ok miod@
2023-03-05Remove ec_GFp_nistp.* prototypes.Joel Sing
This code has been deleted, however the prototypes managed to hang around.
2023-03-05Remove duplicate function prototypes.Joel Sing
2023-03-05Mask off IPL flags before storing the IPL for an interrupt.Patrick Wildt
ok kettenis@ jmatthew@
2023-03-05openssl: make all config structs staticTheo Buehler
These are per-app, so per-file. Most of them already are static, adjust the rest of them.
2023-03-05openssl/cms: zap some trailing whitespaceTheo Buehler
2023-03-05knock out double .Pp;Jason McIntyre
2023-03-05oops, overridden has two d's; apologies ajacoutot for not spotting that.Jason McIntyre
2023-03-05adjust documentation to explain tags, which are still there just in caseMarc Espie
2023-03-05Values for categories that are not set in the environment or that are overridenAntoine Jacoutot
by LANG or LC_ALL are displayed between double quotes. wording by guenther@ ok kn@ jmc@
2023-03-05Add RK356x-specific initialization. Also initialize a few auto modeMark Kettenis
related registers on all supported SoCs. Makes rktemp(4) work on RK356x with U-Boot. ok jmatthew@
2023-03-05Fix mem and FILE leaks in moduli screening.Darren Tucker
If multiple -Ocheckpoint= options are passed, the earlier ones would be overwritten and leaked. If we use an input file that wasn't stdin, close that. From Coverity CIDs 291884 and 291894.
2023-03-05Plug mem leak in moduli checkpoint option parsing.Darren Tucker
From Coverity CID 291894.
2023-03-05Remove unused compat.h includes. We've previously removed a lotDarren Tucker
of the really old compatibility code, and with it went the need to include compat.h in most of the files that have it.
2023-03-05Mask off IPL flags before storing the IPL for an interrupt.Jonathan Matthew
This fixes the IPL calculations in mpic_calc_mask() in the presence of IPL_MPSAFE interrupts such as mvneta(4). ok patrick@ kettenis@ dlg@
2023-03-05Xt -> XrJonathan Gray
2023-03-04Add ytphy(4); pointed out by jmc@Mark Kettenis
2023-03-04Don't whine about invalid start/end values whenKenneth R Westerback
starting to edit an unused GPT partition.
2023-03-04Turns out the RK3566 has a different value in the GPIO_VER_ID registerMark Kettenis
than advertised in the RK3568. This value is present in the Linux driver and implies the new register layout. So handle both values. This makes GPIOs on the RK3566 actually work. ok patrick@
2023-03-04On RK356x many devices need to be explicitly routed to use alternative pinMark Kettenis
muxings. Implement support for this. ok patrick@
2023-03-04Enable ytphy(4) here too.Mark Kettenis
2023-03-04ytphy(4)Mark Kettenis
2023-03-04Add ytphy(4) to files.mii (forgotten in the previous commit).Mark Kettenis
Fix year on my copyright.
2023-03-04enable ytphy(4)Mark Kettenis
2023-03-04Add ytphy(4), a driver for the MotorComm YT8511 PHY.Mark Kettenis
ok deraadt@
2023-03-04Use ISC licence.Mark Kettenis
ok deraadt@
2023-03-04Sync proc.c from vmd(8) to enabled fork + exec for all processes. This givesTobias Heider
each process a fresh and unique address space to further improve randomization of ASLR and stack protector. ok bluhm@ patrick@
2023-03-04openssl enc doesn't really support AEAD ciphers and XTS modeTheo Buehler
Do not display such ciphers in the usage display and error out if they are given. As pointed out by Pauli Dale, the current situation is confusing. Fixes GH issues #786 and #819 ok jsing
2023-03-04Simplify the consistency checks in old_dsa_priv_decode()Theo Buehler
We have long had expensive checks for DSA domain parameters in old_dsa_priv_decode(). These were implemented in a more complicated way than necesary. ok beck jsing
2023-03-04Enforce a lower bound of of EC group order so 80 bits for ECDSATheo Buehler
This makes sure that the elliptic curve is not completely stupid. This is conservative enough: the smallest named groups that we support have an order of 112 bits. ok beck jsing
2023-03-04Cap the number of iterations in ECDSA signingTheo Buehler
ECDSA is essentially the same thing as DSA, except that it is slightly less stupid. Signing specifies an infinite loop, which is only possible with arbitrary ECDSA domain parameters. Fortunately, most use of ECDSA in the wild is based on well-known groups, so it is known a priori that the loop is not infinite. Still, infinite loops are bad. A retry is unlikely, 32 retries have a probability of ~2^-8000. So it's pretty safe to error out. ok beck jsing
2023-03-04Cap the number of iterations in DSA signingTheo Buehler
The DSA standard specifies an infinite loop: if either r or s is zero in the signature calculation, a new random number k shall be generated and the whole thing is to be redone. The rationale is that, as the standard puts it, "[i]t is extremely unlikely that r = 0 or s = 0 if signatures are generated properly." The problem is... There is no cheap way to know that the DSA domain parameters we are handed are actually DSA domain parameters, so even if all our calculations are carefully done to do all the checks needed, we cannot know if we generate the signatures properly. For this we would need to do two primality checks as well as various congruences and divisibility properties. Doing this easily leads to DoS, so nobody does it. Unfortunately, it is relatively easy to generate parameters that pass all sorts of sanity checks and will always compute s = 0 since g is nilpotent. Thus, as unlikely as it is, if we are in the mathematical model, in practice it is very possible to ensure that s = 0. Read David Benjamin's glorious commit message for more information https://boringssl-review.googlesource.com/c/boringssl/+/57228 Thanks to Guido Vranken for reporting this issue, also thanks to Hanno Boeck who apparently found and reported similar problems earlier. ok beck jsing
2023-03-04Use nitems() in the simple iterations over mbr->mbr_prt[].Kenneth R Westerback
No intentional functional change.
2023-03-04Small readability tweak in old_dsa_priv_decode()Theo Buehler
Explicitly check against NULL and turn early return into goto err. ok beck jsing
2023-03-04Call dsa_check_keys() before signing or verifyingTheo Buehler
We already had some checks on both sides, but they were less precise and differed between the functions. The code here is messy enough, so any simplification is helpful... ok beck jsing
2023-03-04Add dsa_check_key() calls on DSA decodingTheo Buehler
When decoding a public or a private key, use dsa_check_key() to ensure consistency of the DSA parameters. We do not always have sufficient information to do that, so this is not always possible. This adds new checks and replaces incomplete existing ones. On decoding the private key we will now only calculate the corresponding public key, if the sizes are sensible. This avoids potentially expensive operations. ok beck jsing
2023-03-04Provide dsa_check_key()Theo Buehler
This is a cheap check that ensures basid parameter consistency per FIPS 186-4: 1 < g < q, that q has the allowed bit sizes 160, 224, 256 and that p is neither too small nor too large. Unfortunately, enforcing the three allowed sizes for p is not possible since the default dsa key generation has not respected this limitation. Instead of checking that p and q are prime, we only check that they are odd. Check that public and private keys, if set, are in the proper range. In particular, disallow zero values. Various versions of these checks have been added to the dsa code over time. This consolidates and extends them and in a subsequent commit wewill replace the incomplete checks. BoringSSL has a similar function of the same name, thanks to David Benjamin for pointing it out. ok beck jsing
2023-03-04Provide DSA_R_INVALID_PARAMETERS error codeTheo Buehler
This has been missing for a while already and will be used in a few upcoming commits. ok beck jsing
2023-03-04syncTheo de Raadt
2023-03-04Mop up ECP_NISTZ256_ASM and OPENSSL_NO_EC_NISTP_64_GCC_128 leftovers.Joel Sing
This is `unifdef -m -DOPENSSL_NO_EC_NISTP_64_GCC_128 -UECP_NISTZ256_ASM` and some manual tidy up.
2023-03-04move to 7.3-betaTheo de Raadt
2023-03-04Toss in some const's to ensure that static data pointed toKenneth R Westerback
by function return values is not fiddled with. No intentional functional change.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-14 16:46:54 +0000