diff options
| author | Luke Hoersten <[email protected]> | 2026-10-26 19:57:11 -0500 |
|---|---|---|
| committer | Luke Hoersten <[email protected]> | 2026-10-26 19:57:11 -0500 |
| commit | 9e1e71d661c9c3df5eaa6b1ce5f0704e470fe96f (patch) | |
| tree | e52f7c0938ec3cf844d00497cfe92de586419187 /mattertimectl/controller/templates/mattertimectl.timer.j2 | |
| parent | 9fb1423d1659fcef72466abde0e0e1af016b923c (diff) | |
openhop/repeater: resolve the 1.1.4 identity-validation review TODO
Checked the actual upstream diffs, not just PR titles: #359/#370's
identity-validation changes only add collision checks between multiple
identities configured on one node (repeater/companion/room-server sharing
a one-byte prefix namespace), unrelated to the single-identity load path.
config.py's _load_or_create_identity_key is unchanged in 1.1.4 and still
silently generates a fresh identity on any read failure instead of
failing loudly, same mechanism as the 2026-08-10 stale-UID incident. Not
introduced or fixed by this bump, so nothing blocks it, but the
underlying fragility remains latent upstream.
Diffstat (limited to 'mattertimectl/controller/templates/mattertimectl.timer.j2')
0 files changed, 0 insertions, 0 deletions