sure, but by that time it would have been determined (with the PID / CID check) that user B is in fact the same as user A.
user B never actually appears in the user list; it is just a connection from user A in which a SUP and an INF are sent. the INF can be trimmed to only containing the PID, CID (and if a custom IP is configured, an IP). once the PID&CID have been verified, that "user B" connection is disconnected and the IP is transferred over to user A's INF. -- You received this bug notification because you are a member of Dcplusplus-team, which is a bug assignee. https://bugs.launchpad.net/bugs/309402 Title: ipv6 support Status in ADCH++: In Progress Status in DC++: In Progress Status in Linux DC++: Confirmed Status in StrongDC++: Fix Committed Bug description: Support for ipv6 as data transport and for client <-> hub communication should be added. As it looks like the ADC protocol already has ipv6 support, that shouldn't require too much work. To manage notifications about this bug go to: https://bugs.launchpad.net/adchpp/+bug/309402/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
