| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
No fields have moved there yet; for now, it's just a placeholder type.
|
| |
|
|
|
| |
This will allow us to add more fields to listener_connection_t
without bloating the other connection types.
|
| |\
| |
| |
| |
| | |
Conflicts:
src/or/config.c
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Returning a tristate is needless here; we can just use the yielded
transport/proxy_type field to tell whether there's a proxy, and have
the return indicate success/failure.
Also, store the proxy_type in the or_connection_t rather than letting
it get out of sync if a configuration reload happens between launching
the or_connection and deciding what to say with it.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Multiple Bridge lines can point to the same one ClientTransportPlugin
line, and we can have multiple ClientTransportPlugin lines in our
configuration file that don't match with a bridge. We also issue a
warning when we have a Bridge line with a pluggable transport but we
can't match it to a ClientTransportPlugin line.
|
| | |
| |
| |
| |
| |
| |
| | |
* Tweaked doxygen comments.
* Changed returns of get_proxy_addrport().
* Ran make check-spaces.
* Various small code tweaks.
|
| | |
| |
| |
| | |
It creates some helper functions that return the proxy type, proxy addr/port, etc.
|
| | |
| |
| |
| |
| | |
Not included in the previous commit, because the implementation is
ugly; I see no other way of doing this though.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
A couple of places in control.c were using connection_handle_write()
to flush important stuff (the response to a SIGNAL command, an
ERR-level status event) before Tor went down. But
connection_handle_write() isn't meaningful for bufferevents, so we'd
crash.
This patch adds a new connection_flush() that works for all connection
backends, and makes control.c use that instead.
Fix for bug 3367; bugfix on 0.2.3.1-alpha.
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
We need this to tell if a given consensus flavor is being downloaded
or not.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This requires the latest Git version of Libevent as of 24 March 2010.
In the future, we'll just say it requires Libevent 2.0.5-alpha or
later.
Since Libevent doesn't yet support hierarchical rate limit groups,
there isn't yet support for tracking relayed-bytes separately when
using the bufferevent system. If a future version does add support
for hierarchical buckets, we can add that back in.
|
| | |
| |
| |
| |
| | |
Clients are now verified to work and build circuits correctly. There
are still a few warnings given here and there that I need to look into.
|
| | |
| |
| |
| |
| |
| | |
Also, set directory connections (linked and otherwise) to use bufferevents.
Also, stop using outbuf_flushlen anywhere except for OR connections.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
These are based strongly on connection_handle_read and
connection_handle_write, but hopefully without so much mixture of IO
logic and Tor logic.
|
| | | |
|
| |/ |
|
| |
|