You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug#35746330 MGMD accept connections before checking its own required certificates
Description:
A MGMD process can be configured to require valid certificates when
starting with configuration parameter [MGM]RequireCertificate=1.
Currently verification happens after listening ports are setup for both
mgm-connections and transporters.
Test `testMgmd -n MgmdWithoutCertificate` fails since client manage to
connect to MGMD before MGMD is shutting down due to no certificates were
detected.
How To Repeat:
Run for example `./mtr ndb.test_mgmd` or
`testMgmd -n MgmdWithoutCertificate`
Fix:
Certificate validation, if required, is done before accepting
any connections (both mgm-protocol and transporters).
First read the relevant configuration before starting either
transporters or mgm-service ports. Then also make sure that
start_transporters propagate the require certificate flag such that
certificate checks are done first if needed.
Change-Id: I5995fc8fb34539ff00fd628be5404d26bf2c00b5
0 commit comments