fix: the check database revokes CONNECT from PUBLIC again (keel#183) #3

Merged
navigator merged 1 commit from fix/check-db-revoke-connect-again into main 2026-10-16 11:56:36 -03:00
Owner

40lnpp-check revokes CONNECT on keel_check from PUBLIC again: only the page's role connects.

19.0-2 kept CONNECT for PUBLIC because keel's reseed probe needed it (keel#183). keel 0.23.33 (Keel-Linux/keel#185) reseeds a pair without CONNECT on every database, and image 19.0-3 carries keel 0.23.39 from trixie-testing. The cross-site test of 19.0-3 reseeds the LNPP pair against this database, so it proves keel#183 on real nodes.

Changelog 19.0 (3) also names the keel fixes the image carries (common#56, keel#106).

Merge only after keel 0.23.39 is in trixie-testing. The appliance gate does not boot this layer: no lnpp layer is on the mirror. The boot proof is the cross-site release test of 19.0-3.

`40lnpp-check` revokes CONNECT on `keel_check` from PUBLIC again: only the page's role connects. 19.0-2 kept CONNECT for PUBLIC because keel's reseed probe needed it (keel#183). keel 0.23.33 (Keel-Linux/keel#185) reseeds a pair without CONNECT on every database, and image 19.0-3 carries keel 0.23.39 from trixie-testing. The cross-site test of 19.0-3 reseeds the LNPP pair against this database, so it proves keel#183 on real nodes. Changelog 19.0 (3) also names the keel fixes the image carries (common#56, keel#106). Merge only after keel 0.23.39 is in trixie-testing. The `appliance` gate does not boot this layer: no lnpp layer is on the mirror. The boot proof is the cross-site release test of 19.0-3.
fix: the check database revokes CONNECT from PUBLIC again (keel#183)
All checks were successful
security / security (pull_request) Successful in 1m34s
tests / tests (pull_request) Successful in 57s
tests / python (pull_request) Successful in 29s
tests / package (pull_request) Successful in 11s
tests / appliance (pull_request) Successful in 15s
tests / stack (pull_request) Successful in 2m26s
5a2b5c8cff
Only the page's role connects to keel_check. 19.0-2 kept CONNECT for
PUBLIC because keel's reseed probe needed it. keel 0.23.33 reseeds a
pair without CONNECT on every database (Keel-Linux/keel#183), and image
19.0-3 carries keel 0.23.36 from trixie-testing. The cross-site test of
19.0-3 reseeds the LNPP pair against this database.
navigator force-pushed fix/check-db-revoke-connect-again from 5a2b5c8cff
All checks were successful
security / security (pull_request) Successful in 1m34s
tests / tests (pull_request) Successful in 57s
tests / python (pull_request) Successful in 29s
tests / package (pull_request) Successful in 11s
tests / appliance (pull_request) Successful in 15s
tests / stack (pull_request) Successful in 2m26s
to 3f303f325c
All checks were successful
tests / python (pull_request) Successful in 26s
tests / tests (pull_request) Successful in 51s
security / security (pull_request) Successful in 1m24s
tests / appliance (pull_request) Successful in 12s
tests / package (pull_request) Successful in 5s
tests / stack (pull_request) Successful in 2m1s
2026-10-16 09:07:44 -03:00
Compare
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Keel-Linux/keel-lnpp!3
No description provided.