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
As this is security-related software, I recommend we add a test to check that when connecting to a DNSChain server via HTTPS with an invalid certificate, the connection is rejected client-side with an appropriate error.
May need to mock this properly.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5422412-unit-test-for-invalid-https-cert?utm_campaign=plugin&utm_content=tracker%2F7170449&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F7170449&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
I won't commit to adding HTTPS support to DNSChain, but maybe if I'm really productive, I can get around to to it after adding fingerprint verification to the pydnschain node. Anywho, if no-one else's has gotten to it by the time I've polished off the rest of my issues, I'll start on it.
As this is security-related software, I recommend we add a test to check that when connecting to a DNSChain server via HTTPS with an invalid certificate, the connection is rejected client-side with an appropriate error.
May need to mock this properly.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5422412-unit-test-for-invalid-https-cert?utm_campaign=plugin&utm_content=tracker%2F7170449&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F7170449&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: