linuxdcpp-team team mailing list archive

[eMTee <841189@xxxxxxxxxxxxxxxxxx>]

Crise's very good assessment in post #8 still holds.

Inside the DC++ team we call this "NMDC feature freeze" something that
is in effect since cca. 2008. It means that no new features and NMDC
protocol compatibility should remain as it was in the point of time when
the freeze imposed. The only exceptions are possible security issues.

However, the non-intrusiveness of H<>C TLS might make it possible to be
considered for an addition as it may not break the above commitment:

- it doesn't change anything at the protocol level
- can be considered a security issue (see post #1)
- has constantly been requested by the hub owners due to security considerations
- is better for DC++ users (so they can connect all the hubs appearing in public hublists)

C<>C TLS is still a no go; applying the current client implementations
would break both the line protocol, connectivity and compatibility
freeze requirements.

-- 
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