linuxdcpp-team team mailing list archive

[Crise <1543595@xxxxxxxxxxxxxxxxxx>]

In case Night happens to look at this as I deliberated on what to do
about KeyPrint checks in general I opted to use the same logic for
checking KeyPrints for client connections regardless of the type of
connection. In the end while post-handshake check is not ideal it is a
cheap insurance against connectivity issues and makes it easier to
diagnose if they do keep popping up.

** Changed in: dcplusplus
       Status: New => Fix Committed

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

Title:
  Issues with encrypted transfers

Status in AirDC++:
  Fix Released
Status in DC++:
  Fix Committed

Bug description:
  1. Join an ADCS hub with at least two ncdc users
  2. Download filelist from both users
  3. Disconnect both connections
  4. Download filelist from both users again

  The second download will fail. I suspect that this is because ncdc
  generates certificates with a hardcoded subject (Jucy does that as
  well).

  The behavior is a bit random and significantly worse on Linux, as all
  connections to other ncdc users will fail there after storing the
  certificate of the first user. Obviously it will pick the oldest
  certificate with matching subject and issuer from the store instead of
  the most recently added one, also breaking connectivity with other
  DC++ users after they have regenerate their certificates (Linux only).

  Tested with the latest build from the archive
  (dcpp_b20151221_1704_rev_7ed142dac13a).

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