linuxdcpp-team team mailing list archive

[Kcchouette <841189@xxxxxxxxxxxxxxxxxx>]

@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

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/841189

Title:
  Encryption under NMDC

Status in DC++:
  New

Bug description:
  Well it seems like a popular demand so lets drag this topic thru the
  mud once again

  as we all know it is possible to encrypt c-c transfers but now there
  is also the option to encrypt c-h traffic aswell and since nmdc is
  predominant on direct connect it would benefit dc++ too actually
  encrypt this traffic since mods already have this support again
  strongdc++ along with all its subclients

  request taken from:
  http://www.adcportal.com/forums/viewtopic.php?f=13&t=769

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/841189/+subscriptions