Support for the IBM FireGL-UX boards.
The last piece of the puzzle was to pass the right flags at the first init
microcode call, in order to correctly completely initialize its own "softc".
This makes character drawing operation point to the right offset within the
frame buffer.
Thanks to Daniel Dickman for noticing the microcode had a specific code path
when some bits (which we did not set) in the init flags were set.
Battery notifications only require the low byte, mask the rest.
This silences unknown battery notification messages on some machines.
ok mlarkin@, deraadt@
_shutdown group members can run shutdown with their own environment
including PATH, which is not good. Reuse the (extremely, maybe too restricted?)
restricted_environ[] used by the the wall(1) run.
from Acts1631
Properly quote the hostname before putting it into rc.firsttime(8)
Before dhcpleased/engine.c r1.72 invalid host- or domain-name values
could make it through lease files and the installer and be placed in
shell code on first boot.
Use quote() over single quotes to handle special characters;
they should no longer make it to the installer, though.
from Acts1631
OK afresh1
While ld.so cannot lock mappings in the normal dlopen() case, we can apply
the same immutable protection as load-time shared libraries for dlopen'd
libraries mapped with RTLD_NODELETE.
With refactoring and comments by deraadt@, thanks!
Factor the code used by ucom(4) to forcibly detach processes from the tty
about to get removed upon detach to a ttydetach() routine, and make use of it
also when deleting wsdisplay screens, as well as com at pcmcia.
Bug report for wsdisplay by OpenAI.
Work by deraadt@, polishing by me.
rpki-client: and another time BGPsec Router Keys are special
This time the story is that proc_parser_cert() and proc_parser_root_cert()
hang the cert they return off a tree in the parser, but proc_parser_cert()
does not take ownership of a BRK. This is yet another wart coming from the
fact that you have no clue what a .cer is going to be.
Pointed out by Ties de Kock
ok claudio
Ignore invalid hostnames and domainnames.
Nothing in base looks at these but they still end up in the lease file
where unprepared scripts might pick them up.
Pointed out by Acts1631.
OK krw, kn
error if get_unused_fd_flags() is called without O_CLOEXEC set
Previously this was a KASSERT. landry saw it trigger on inteldrm
(Kaby Lake). Caller is unclear, likely DRM_IOCTL_PRIME_HANDLE_TO_FD.
rpki-client: adjust comment regarding TA tie breakers
Tie breaking is now in an RFC, so remove claim to the contrary and our
logic is now the logic of said RFC.
ok job
Initialize m_len after MGET() and properly enforce the MRU limit.
Previously, the uninitialized m_len could cause a KASSERT().
reported Acts1631, input mvs
ok mvs
Update RPKI Trust Anchor Tiebreaker reference
As luck would have it, on the very day this spec got published as RFC,
one of the RIRs helped demonstrate the usefulness of the concept in the
production environment.
https://www.rfc-editor.org/rfc/rfc10097.html with Theo Buehler & Ties de Kock
Rpki-client instances globally did not suffer from the below RPKI
certification service outage.
"""
RPKI repositories unavailable - Incident Report for RIPE NCC
Future Dated Trust Anchor Certificate temporarily in the RPKI Repository
The RPKI Trust Anchor (TA) Certificate is signed using an offline
machine that's disconnected from the Internet. As the clock may drift
on this machine while it's turned off, the normal procedure is to
[15 lines not shown]
Update RPKI Trust Anchor Tiebreaker reference
As luck would have it, on the very day this spec got published as RFC,
one of the RIRs helped demonstrate the usefulness of the concept in the
production environment. Rpki-client instances did not suffer from the
below certification service outage.
with tb@
"""
RPKI repositories unavailable - Incident Report for RIPE NCC
Future Dated Trust Anchor Certificate temporarily in the RPKI Repository
The RPKI Trust Anchor (TA) Certificate is signed using an offline
machine that's disconnected from the Internet. As the clock may drift
on this machine while it's turned off, the normal procedure is to
recalibrate it manually before signing a new certificate. During the
re-signing on 18 November 2026, the clock on the TA machine was set
[13 lines not shown]
rpki-client: reject CustomerASID 0 in CCR as well
Add a check to CCR's parse_aspa_payloads() analogous to the one added to
aspa_parse_econtent() in aspa.c 1.50.
ok job
Update to zlib 1.4
ok deraadt
The security fixes are already in tree, the remaining relevant fixes
for OpenBSD include these:
- Deliver all gzip data before reporting error
- Fix truncated stream detection in gzread()
- Fix pending skip handling in gzread()
- Fix loss of zero fill on repeated gzseek()'s when writing
- Fix inaccurate total_in after Z_NEED_DICT returned
- Detect and report bad deflateSetDictionary() calls
- Avoid undefined behaviors in C language usage
- Don't assume NULL is defined in compress.c and uncompr.c
- Clarify documentation