[tor-bugs] #32830 [Core Tor]: Relay_extended - hash and padding - specs are wrong or unclear

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#32830: Relay_extended - hash and padding - specs are wrong or unclear
---------------------+--------------------------
 Reporter:  Aymeric  |          Owner:  (none)
     Type:  defect   |         Status:  new
 Priority:  Medium   |      Component:  Core Tor
  Version:           |       Severity:  Normal
 Keywords:           |  Actual Points:
Parent ID:           |         Points:
 Reviewer:           |        Sponsor:
---------------------+--------------------------
 I noticed recently plenty of 'unrecognized' relay_extended messages for
 node-Tor project while everything was working fine in the past after I
 updated the code and made it modular (and some abnormal delays to
 establish circuits), see also http://peersm.com/peersm2 this is temporary
 but I had to put a lot of debug stuff to find out what was going on

 Finally I figured out why: unlike what is writen in the main Tor specs the
 hash is calculated not only with the real payload of the relay_extended
 messages but includes also the padding (apparently starting with 00000000,
 not sure where it comes from neither where it is specified)

 This looks quite strange, what is the rationale for this, is it a bug, why
 is it not documented and does it impact other types of messages?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32830>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs