mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-23 22:47:12 +01:00
Fix a "shouldn't have reached this" warning in connection_edge.c
This was bug 20630; bugfix on f3e158ed
where I thought I was
committing a documentation-only fix but instead messed up the
control flow too.
This commit is contained in:
parent
7918e219d4
commit
307d244640
1 changed files with 3 additions and 5 deletions
|
@ -1627,11 +1627,9 @@ connection_ap_handshake_rewrite_and_attach(entry_connection_t *conn,
|
|||
}
|
||||
tor_assert(!automap);
|
||||
rep_hist_note_used_resolve(now); /* help predict this next time */
|
||||
}
|
||||
} else if (socks->command == SOCKS_COMMAND_CONNECT) {
|
||||
/* Now see if this is a connect request that we can reject immediately */
|
||||
|
||||
/* Now see if this is a connect request that we can reject immediately */
|
||||
if (socks->command == SOCKS_COMMAND_CONNECT) {
|
||||
/* Special handling for attempts to connect */
|
||||
tor_assert(!automap);
|
||||
/* Don't allow connections to port 0. */
|
||||
if (socks->port == 0) {
|
||||
|
@ -1771,7 +1769,7 @@ connection_ap_handshake_rewrite_and_attach(entry_connection_t *conn,
|
|||
rep_hist_note_used_resolve(now); /* help predict this next time */
|
||||
/* no extra processing needed */
|
||||
} else {
|
||||
/* We should only be doing CONNECT or RESOLVE! */
|
||||
/* We should only be doing CONNECT, RESOLVE, or RESOLVE_PTR! */
|
||||
tor_fragile_assert();
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue