fix: the check database revokes CONNECT from PUBLIC again (keel#183) #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/check-db-revoke-connect-again"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
40lnpp-checkrevokes CONNECT onkeel_checkfrom 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
appliancegate 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.5a2b5c8cff3f303f325c