Comment 7 for bug 841189

@Delion: One problem that point @Crise by his comment is that even if "ApexDC++ seems to work just fine [...] DC++not", like NMDCs is not written in specification -> "whether DC++ or any other client chooses to implement that or some other variant of TLS for NMDC is up to every project individually."

Here in you screenshot you (Delion) seem to underligne that C-C in NMDCs hub using TLS fails, isn't it?

But the specification only state "URI scheme is dchub:// for unencrypted and nmdcs:// for encrypted connections."[1], so here the term "encrypted connections" can just be the login between Client-Server...

And so by extension (and adding that I understand from Crise) "the implementation of TLS inside NMDC for this or that component is up to the developer of the DC client"

[1]: https://github.com/direct-connect/protocols/blob/master/nmdc/nmdc.md#general