rumqttc: Enable native tls TlsConnector support.

[xiaocq2001]

Type of change

Resolves #866.

New feature (non-breaking change which adds functionality)

• Transport::tls_with_config now accepts native_tls::TlsConnectorBuilder instance as input, to customize options

Checklist:

• Formatted with cargo fmt
• Make an entry to CHANGELOG.md if it's relevant to the users of the library. If it's not relevant mention why.

[xiaocq2001]

Considering that the Native could be used to simplify native configuration to use OS settings, and there may be compatible issue, I added new NativeBuild to accept builder as input.

[de-sh]

Hopefully no one depends on TlsConfiguration being Debug, Transport ain't so LGTM

[coveralls]

Pull Request Test Coverage Report for Build 9561251742

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 4 (0.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.008%) to 36.123%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
rumqttc/src/tls.rs	0	1	0.0%
rumqttc/src/lib.rs	0	3	0.0%

Totals
Change from base Build 9290350918:	-0.008%
Covered Lines:	5970
Relevant Lines:	16527

---

💛 - Coveralls

[de-sh]

Since we don't do much with the Builder under the hood, why not just ask the user to build it first?

[xiaocq2001]

Since we don't do much with the Builder under the hood, why not just ask the user to build it first?

I just keep align with the implement for rustls where ClientConfig is passed to build connection.

I saw the updates, that's fine, just accepted.

[xiaocq2001]

Added wss (WebSocket Secure) support.
tls-native works fine connecting to mosquitto public broker.

Facing issue when using rustls, it always fail with "failed to lookup address information: Name or service not known", I guess some specific certification should be used?

I found the issue wss_with_config must be used instead of tls_with_config. The example works fine now.

[xiaocq2001]

It's approved and tests are green, is there any more thing I need to do to let it merged?

BTW, is there any timeline for next rumqttc release and crate update?

[swanandx]

It's approved and tests are green, is there any more thing I need to do to let it merged?

hey, thanks for your patience and reminder :) actually we got caught up with other work and so this was missed.

BTW, is there any timeline for next rumqttc release and crate update?

due to same reason of not having much bandwidth, can't commit to any specific date rn, but should be quite soon.

[de-sh]

Please move changes regarding wss from this PR to another

[de-sh]

Post mentioned changes please open a separate PR to address native-tls support for websockets

[xiaocq2001]

Please move changes regarding wss from this PR to another

OK, wss example removed. I'll create another PR for websocket changes on main right after this one is merged.

[xiaocq2001]

Thanks.
WSS updates are here, please review.
#881