diff options
author | Nick Mathewson <nickm@torproject.org> | 2011-08-02 10:48:39 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2011-08-02 10:48:39 -0400 |
commit | 6596aa022f03bad34a3ee9cbd627fefe55c01d54 (patch) | |
tree | cf6ea9a451ed365e59c5b8a0389e614636672f90 /src/or/or.h | |
parent | 478785a762ebbfc1c95192d9cfd4617bd87d9d16 (diff) | |
download | tor-6596aa022f03bad34a3ee9cbd627fefe55c01d54.tar.gz tor-6596aa022f03bad34a3ee9cbd627fefe55c01d54.zip |
Implement protocol-type isolation correctly.
Previously we'd just looked at the connection type, but that's
always CONN_TYPE_AP. Instead, we should be looking at the type of
the listener that created the connection.
Spotted by rransom; fixes bug 3636.
Diffstat (limited to 'src/or/or.h')
-rw-r--r-- | src/or/or.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h index d6d8c7a050..150971b5fb 100644 --- a/src/or/or.h +++ b/src/or/or.h @@ -3382,6 +3382,8 @@ struct socks_request_t { uint8_t auth_type; /** What is this stream's goal? One of the SOCKS_COMMAND_* values */ uint8_t command; + /** Which kind of listener created this stream? */ + uint8_t listener_type; size_t replylen; /**< Length of <b>reply</b>. */ uint8_t reply[MAX_SOCKS_REPLY_LEN]; /**< Write an entry into this string if * we want to specify our own socks reply, |