dotnet / dotnet/MQTTnet

Certificate-Weakening TlsOptions have no effect on web socket connections

Open
#858 1 comment 0 reactions 0 assignees View on GitHub
bug documentation
Dominant language
C#
Stars
5.1k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

I noticed that the "certificate weakening" TlsOptions like IgnoreCertificateChainErrors, IgnoreCertificateRevocationErrors, AllowUntrustedCertificates and CertificateValidationCallback have no effect when using web socket connections.

I understand this is because the underlying api (System.Net.WebSockets) does not support this (at least not in all target frameworks), but I think it should be noted somewhere - that would have saved me several hours of trial and error...

Contributor guide

No contributing guide indexed for this repository

Research direction

Inspect the project documentation for TlsOptions and websocket connections, starting with the existing descriptions of certificate validation settings. Document that these certificate-weakening options have no effect for websocket connections because of the underlying System.Net.WebSockets API; done means users can find and understand this limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.