sshd-session: For libwrap, only check "sshd"
Previously, both "sshd" and "sshd-session" were checked, which
does not work for some hosts.allow configurations, as described
in PR bin/60512.
Instead, only check "sshd" again as done before sshd-session was
introduced; "sshd-session" is an internal implementation detail,
and we should just use "sshd" consistently.
OK christos
zoneminder: Patrol comments and clean up
NFCI -- this is just aligning comments/explanations to reality and
somewhat simplifing the PKGNAME/DISTNAME/GITHUB_TAG situation.
openssl: Install byteorder.h, hpke.h, and ml_kem.h.
Sort INCS and format it to make detecting changes a little easier by
diff from:
ls ../../dist/include/openssl | sed -E -e 's,(\.in)?$, \\,'
Nix separate sections for IDEA/MDC2/RC5; the patents on these have
long since expired so it's not worth mentioning them separately.
(The algorithms are also all obsolete, but if OpenSSL ships the
header files, we should do so too.)
PR lib/60511: openssl set lists differences to pkgsrc
p0f: Update to 3.09b
Update to the latest release 3.09b.
Still not building, there is a bit of work to do because the build
system is completely changed!
Bracket I/O from or to the backing store with fstrans_start_lazy()
so the fss device doesn't block before the file system is suspended.
Should fix some deadlocks with revokation of ttys.
PR kern/59663 (ffs_snapshot_read -> uvm_fault (or pool page empty)
p0f: Import p0f-2.0.8nb1
P0f v2 is a versatile passive OS fingerprinting tool. P0f can identify the
operating system on:
- machines that connect to your box (SYN mode),
- machines you connect to (SYN+ACK mode),
- machine you cannot connect to (RST+ mode),
- machines whose communications you can observe.
P0f can also do many other tricks, and can detect or measure the following:
- firewall presence or masquerading (useful for policy enforcement),
- presence of a load balancer setup,
- the distance to the remote system and its uptime,
- other guy's network hookup (DSL, OC3, avian carriers) and his ISP.
Imported from security/p0f.
Don't use pmap_update in pmap_{page_protect,clear_attribute} as the
PMAP_DEFERRED_ACTIVATE logic doesn't apply. Instead create a new
pmap_shootdown which performs the necessary shootdowns for
PMAP_TLB_NEED_SHOOTDOWN architectures.