Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1557 closed Bug (fixed)

handshake peer-id doesn't match the peer-id sent in the tracker announce

Reported by: charles Owned by: charles
Priority: Normal Milestone: 1.41
Component: libtransmission Version: 1.40
Severity: Major Keywords: protocol
Cc:

Description

From ​the spec:

If the initiator of the connection receives a handshake in which the peer_id does not match the expected peerid, then the initiator is expected to drop the connection. Note that the initiator presumably received the peer information from the tracker, which includes the peer_id that was registered by the peer. The peer_id from the tracker and in the handshake are expected to match.

Transmission is currently not doing this. It uses a different peer_id in the handshake than it does in the announce.

Change History (5)

comment:1 Changed 13 years ago by charles

  • Component changed from Transmission to libtransmission
  • Owner set to charles
  • Status changed from new to assigned

comment:2 Changed 13 years ago by charles

fix committed to trunk in r7266.

comment:3 Changed 13 years ago by charles

fix committed to 1.4x branch in r7267.

comment:4 Changed 13 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:5 Changed 13 years ago by charles

  • Keywords protocol added

fix committed to 1.3x branch in r7282.

Note: See TracTickets for help on using tickets.