| commit | 3ff092391b065561da339dc05614beb4e586a4d8 | |
| author | Nick Mathewson <nickm@torproject.org> | |
| Thu, 4 Mar 2010 23:37:40 +0000 (4 18:37 -0500) | ||
| committer | Nick Mathewson <nickm@torproject.org> | |
| Thu, 4 Mar 2010 23:37:40 +0000 (4 18:37 -0500) | ||
| tree | 5bc71a75744eff4b49bdae031142e57419b447e7 | treesnapshot (tar.gz zip) |
| parent | 404af59ed553e7c1f4cef6668b6832e0bd1a8956 | commitdiff |
Apply Roger's bug 1269 fix.
From http://archives.seul.org/tor/relays/Mar-2010/msg00006.html :
As I understand it, the bug should show up on relays that don't set
Address to an IP address (so they need to resolve their Address
line or their hostname to guess their IP address), and their
hostname or Address line fails to resolve -- at that point they'll
pick a random 4 bytes out of memory and call that their address. At
the same time, relays that *do* successfully resolve their address
will ignore the result, and only come up with a useful address if
their interface address happens to be a public IP address.
From http://archives.seul.org/tor/relays/Mar-2010/msg00006.html :
As I understand it, the bug should show up on relays that don't set
Address to an IP address (so they need to resolve their Address
line or their hostname to guess their IP address), and their
hostname or Address line fails to resolve -- at that point they'll
pick a random 4 bytes out of memory and call that their address. At
the same time, relays that *do* successfully resolve their address
will ignore the result, and only come up with a useful address if
their interface address happens to be a public IP address.
| ChangeLog | diffblobblamehistory | |
| src/or/config.c | diffblobblamehistory |