mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 05:03:43 +01:00
We were already rejecting relay begin cells with destination port
of 0. Now also reject extend cells with destination port or address of 0. Suggested by lark. svn:r18812
This commit is contained in:
parent
5cb2e4efca
commit
5d50bc3e1d
@ -38,6 +38,9 @@ Changes in version 0.2.1.13-alpha - 2009-02-09
|
||||
manner, to avoid platform-dependent behavior on malformed input.
|
||||
- Build correctly when configured to build outside the main source
|
||||
path. Patch from Michael Gold.
|
||||
- We were already rejecting relay begin cells with destination port
|
||||
of 0. Now also reject extend cells with destination port or address
|
||||
of 0. Suggested by lark.
|
||||
|
||||
o Minor bugfixes (on 0.2.1.x):
|
||||
- Don't re-extend introduction circuits if we ran out of RELAY_EARLY
|
||||
|
@ -762,7 +762,13 @@ circuit_extend(cell_t *cell, circuit_t *circ)
|
||||
id_digest = cell->payload+RELAY_HEADER_SIZE+4+2+ONIONSKIN_CHALLENGE_LEN;
|
||||
tor_addr_from_ipv4h(&n_addr, n_addr32);
|
||||
|
||||
/* First, check if they asked us for 0000..0000. We support using
|
||||
if (!n_port || !n_addr32) {
|
||||
log_fn(LOG_PROTOCOL_WARN, LD_PROTOCOL,
|
||||
"Client asked me to extend to zero destination port or addr.");
|
||||
return -1;
|
||||
}
|
||||
|
||||
/* Check if they asked us for 0000..0000. We support using
|
||||
* an empty fingerprint for the first hop (e.g. for a bridge relay),
|
||||
* but we don't want to let people send us extend cells for empty
|
||||
* fingerprints -- a) because it opens the user up to a mitm attack,
|
||||
|
Loading…
Reference in New Issue
Block a user