• Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Ingress Security
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Monguard-OpenSSL and monguard-s2n currently have some mutually exclusive configuration options (e.g., opensslCipherConfig, opensslCipherSuiteConfig, enableHandoff). As a result, hot restart won't work when upgrading to a monguard-s2n process from monguard-openssl because the latter will not recognize an OpenSSL-specific configuration file.

      We should remove any TLS backend-specific guards on the configuration file so that both variants of monguard are able to start up with any file. However, they should emit a warning log and potentially start up in a mode that doesn't accept any new connections if it has any TLS config options that mismatch with the compiled TLS library.

      Then, we should write a test that mocks the entire proposed upgrade path:

      1. Start monguard-openssl with some OpenSSL-specific options set.
      2. Accept connections normally.
      3. Perform a config hot-reload that applies s2n-specific options (this would likely be just enable_handoff and s2n_policy )
      4. Initiate the hot-restart procedure, with monguard-s2n set as the target upgrade binary
      5. Ensure that monguard-s2n is running and listening for new connections. It ignores OpenSSL-specific options.
      6. Ensure that monguard-openssl shuts down without incident.
      7. Ensure that clients connected to monguard-openssl were forced to disconnect but are able to reconnect without any configuration changes on their end (simulating a driver connection pool reconnect).

            Assignee:
            Unassigned
            Reporter:
            Varun Ravichandran
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: