CVSROOT: /cvs
Module name: src
Changes by: [email protected] 2026/11/18 17:03:33
Modified files:
usr.sbin/rpki-client: rpki-client.8
Log message:
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
recalibrate it manually before signing a new certificate. During the
re-signing on 18 November 2026, the clock on the TA machine was set
to a future time and this was not corrected according to the normal
procedure.
As a result, the new TA certificate had "notValidBefore" set to 14:25:43
UTC and it was published to the publication server at 14:10:02 which
generated the new delta in the RRDP repository at 14:10:36 and updated
rsync repository at 14:11:10.
Validators that downloaded the updated TA certificate between
approximately 14:11 and 14:25 reported an invalid TA certificate with
the whole RIPE NCC RPKI tree effectively becoming marked as invalid.
"""
source: https://status.ripe.net/incidents/z04tkkl8m3ws