feat(client): configurable certificate verification #320
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description & motivation
Currently the client always validates the certificate. This is secure behaviour and should continue to be the default.
In certain conditions, for example when using specklepy with a server in a test environment, the server may not be able to present a valid certificate.
In these conditions it is helpful to be able to disable certificate verification.
Changes:
To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References