Add TLS support for CTLog server #1523
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Hello, |
3edaf50 to
0b4f592
Compare
|
/gcbrun |
Signed-off-by: Firas Ghanmi <fghanmi@redhat.com>
|
/gcbrun |
|
Hey @fghanmi one tip to make incremental github reviews easier for the reviewer: once a commit has been proposed, make any further changes as commits on top of that instead of squashing the commits together and force pushing. This makes it easier to see that recent changes have not affected code that a reviewer may already have looked at. The commits can all be squashed together at the point where the PR is merged into the main branch. |
Signed-off-by: Firas Ghanmi <fghanmi@redhat.com>
Summary
This pull request introduces support for enabling TLS security for CTLog. By adding two new command-line flags
--tls_certificateand--tls_keywhich represents the path to server TLS certificate and private key respectively.And also implementing the necessary logic to handle TLS, this update enhances the security of CTLog.
Release Note
New Flags:
--tls_certificateand--tls_keyto specify the file path for service certificate and private key.Behavior: If
--tls_certificateand--tls_keyflags are not both provided, the system will default to insecure connections.Security: This update significantly enhances the security of data in transit by enabling TLS.
Resolves Issue: #1522
Checklist