Custom Query (25123 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (130 - 132 of 25123)

Ticket Resolution Summary Owner Reporter
#131 Implemented Tor dies unnecessarily if its IP address is private goodell
Description

After reading the config, Tor commits suicide if its IP address is considered private, even if NoPublish == 1.

[Automatically added by flyspray2trac: Operating System: All]

#132 Implemented convert "router.exit" requests to "or-address.router.exit" goodell
Description

Connection requests for "router.exit" should not simply be terminated. Instead, they should be interpreted as requests to services running on the OR in question. I am including a patch that prepends the address of the OR, as provided by the descriptor, to requests of the form "router.exit".

I have tested this patch thoroughly, and it works.

Note that this feature might provide an alternative way of resolving the oft-asked question on the mailing list "how do I access a resource on a particular server but know that I am exiting Tor from a node running on that server?"

<pre> diff -u or/connection_edge.c or.patch/connection_edge.c --- or/connection_edge.c 2005-05-07 01:55:06.000000000 -0400 +++ or.patch/connection_edge.c 2005-05-09 13:01:47.000000000 -0400 @@ -914,7 +914,13 @@

if (addresstype == EXIT_HOSTNAME) {

/* .exit -- modify conn to specify the exit node. */ char *s = strrchr(socks->address,'.');

if (!s
s[1] == '\0') {

+ if (!s) { + char *orig = tor_strdup(socks->address); + strlcpy(socks->address, "127.0.0.1.", sizeof(socks->address)); + strlcat(socks->address, orig, sizeof(socks->address)); + s = strrchr(socks->address,'.'); + } + if (s[1] == '\0') {

log_fn(LOG_WARN,"Malformed exit address '%s'. Refusing.",

safe_str(socks->address));

connection_mark_unattached_ap(conn, END_STREAM_REASON_TORPROTOCOL);

</pre>

[Automatically added by flyspray2trac: Operating System: All]

#133 Fixed descriptors have address 0.0.0.0 until directory fetch goodell
Description

Descriptors received from the controller via the POSTDESCRIPTOR directive are interpreted to have address 0.0.0.0. This is corrected at the time of the next periodic directory fetch, at which point the addr field of the routerinfo_t is populated with the correct address from the descriptor. Note that even if no descriptors with the same nickname or identity as the one received from the controller are received from the periodic directory fetch, the address of the descriptor received from the controller will apparently be changed to be the right one.

Indeed, this means that sending the HUP signal to the Tor process will always fix the problem, but ideally we should figure out why directory fetches are necessary to fix descriptors passed in from the controller.

[Automatically added by flyspray2trac: Operating System: All]

Note: See TracQuery for help on using queries.