Opened 13 years ago
Closed 13 years ago
#3274 closed Bug (fixed)
When connecting with a DHT-enabled peer, we send our port message out-of-order
Reported by: | charles | Owned by: | charles |
---|---|---|---|
Priority: | Normal | Milestone: | 2.00 |
Component: | libtransmission | Version: | 1.70 |
Severity: | Major | Keywords: | backport-1.9x |
Cc: |
Description
The [ have all | have none | have bitfield ] message needs to come before the port message that we send to DHT-enabled peers, but it comes first. Looks like the original DHT patch introduced this bug -- so Juliusz wrote it, and I approved & committed it. Bah.
It's hard to tell how much impact this bug has. My best guess is that it will only affect peer connections with very old clients, such as those not supporting LTEP. Nevertheless, every peer is important in small swarms, so I'm marking this as a "Major" severity bug.
Change History (3)
comment:1 Changed 13 years ago by charles
- Status changed from new to assigned
comment:2 Changed 13 years ago by charles
- Keywords backport-1.9x added
comment:3 Changed 13 years ago by charles
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
fixed in trunk for 2.00 by r10737