Remove amountpipekva variable and related computations. This variable used
to matter until rev 1.19 27 years ago, when the "direct write" code was
removed.
net/teleport: avoid picking up security/openpam as a hidden dependency
Make sure that PAM always stays disabled. The upstream Makefile enabled
PAM support unconditionally if the header security/pam_appl.h was present
when the build started. The build could fail later on in case openpam gets
uninstalled before pam.go gets compiled, which is how this hidden dependency
was detected in a bulk build by naddy@.
xmlsec: use X509_STORE_get1_objects/ASN1_TIME_to_tm
X509_STORE_get0_objects() is not thread safe. ASN1_TIME_to_tm() has been
available for ~5 years, let's use that rather than a reimpl.
Upstream landed a more intrusive version of this in #1440
rpki-client: drop some redundant parentheses in return statements
Almost all of the code omits them, so be consistent. The remaining
two are special: to_encode() is rather complicated and CBS_strdup()
is upstream code.
ok job
Limit impact of quadratic workload caused by duplicate references from manifests
Jacobsen et al., 2026, and, independently, eur1ka, reported that a set
of colluding CAs could cause significant workload by publishing multiple
manifests which all reference the same set of signed objects inside the
same caRepository.
In practice there should never be more than two manifests in any given
caRepository directory since the norm is that caRepositories are not
shared across CAs. In the normal course of operation two valid manifests
existing in the same repository directory only occurs during a keyroll
(RFC 6489), as is also pointed out in RFC 9286, section 2.
This changeset introduces a limit of 20 manifests per Trust Anchor per
caRepository. If this threshold is exceeded, any newly discovered CAs
pointing into that caRepository are considered bad, discarded, and a
counter is incremented in the OpenMetrics output.
With & OK tb@
