Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use PKCS12 keystore as a truststore for non-standard CA and self-sign certificates #716

Open
usmansaleem opened this issue Feb 16, 2023 · 0 comments
Labels
doc-change-required Indicates an issue or PR that requires doc to be updated enhancement New feature or request good first issue Good for newcomers TeamCerberus Under active development by TeamCerberus @Consensys

Comments

@usmansaleem
Copy link
Collaborator

In context of enabling TLS in Web3Signer, it currently uses "known certificate" text file that contains common name and certificate fingerprints (sha256) to trust the self-signed TLS certificates.

The typical approach in Java applications is to use a PKCS12 formatted truststore to trust the non-standard CA or self-signed certificates.

Consider deprecating or removing "known certificates" approach and migrate to using PKCS12 based truststore for TLS mutual authentication.

@usmansaleem usmansaleem added doc-change-required Indicates an issue or PR that requires doc to be updated enhancement New feature or request good first issue Good for newcomers labels Feb 16, 2023
@jframe jframe added the TeamCerberus Under active development by TeamCerberus @Consensys label Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-change-required Indicates an issue or PR that requires doc to be updated enhancement New feature or request good first issue Good for newcomers TeamCerberus Under active development by TeamCerberus @Consensys
Projects
None yet
Development

No branches or pull requests

2 participants