Custom Query (24542 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (85 - 87 of 24542)

Ticket Resolution Summary Owner Reporter
#1290 fixed networkstatus warning comes out of nowhere arma
Description

... Feb 12 00:47:11.144 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'urras' at 208.83.223.34:443 (contact 1024D/9D0FACE4 Jacob Appelbaum <jacob@…>; identity 80550987E1D626E3EBA5E5E75A458DE0626D088C) Feb 12 00:47:11.145 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'moria1' at 128.31.0.34:9131 (contact 1024D/28988BF5 arma mit edu; identity D586D18309DED4CD6D57C18FDB97EFA96D330566) Feb 12 00:47:11.145 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'dizum' at tor.dizum.com:80 (contact 1024R/8D56913D Alex de Joode <adejoode@…>; identity E8A9C45EDE6D711294FADF8E7951F4DE6CA56B58) Feb 12 00:47:11.145 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'gabelmoo' at 80.190.246.100:8180 (contact 1024D/F7C11265 Karsten Loesing <karsten dot loesing AT gmx dot net>; identity ED03BB616EB2F60BEC80151114BB25CEF515B226) Feb 12 00:47:11.146 [Warning] 2 unknown, 7 missing key, 0 good, 0 bad, 2 no signature, 4 required Feb 12 00:47:11.146 [Info] networkstatus_set_current_consensus(): Not enough certificates to check networkstatus consensus Feb 12 00:47:11.146 [Notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus. Feb 12 00:47:11.147 [Info] connection_dir_client_reached_eof(): Successfully loaded consensus ...

People running on log-level notice will just see that [warning] come out of nowhere. Looks like we got our severity screwed up there.

[Automatically added by flyspray2trac: Operating System: All]

#1292 fixed Tor version in About screen is wrong n8fr8 Sebastian
Description

Under 3rd-Party-Software, it says:

Tor v2.0.x: https://www.torproject.org

It should say the exact version of Tor, and Tor version numbers start with 0.

[Automatically added by flyspray2trac: Operating System: All]

#1294 fixed Bandwidth weights absent when D=0 mikeperry mikeperry
Description

When the directory authorites vote that there are insufficient Exit nodes for them to be labled as both Exit and Guard, the authorities fail to add a bandwidth-weights line in consensus method 9. This has two problems:

  1. We could actually create weights in may cases when this does happen.
  1. This decision is made on the individual consensus *votes*, not the final consensus. There have been several

situations so far when the authorites voted not to have Guard+Exit even though there was sufficient exit bandwidth in the consensus, and vice-versa.

The problem is that this check probably is a good idea to perform, because of the large numbers of existing clients that we want to avoid using Exits-as-Guards with until they update to the new weighting system.

The correct solution should be to tweak the Guard flag such that it produces a fixed amount of Guard-flagged nodes in the actual consensus. We should allow the weights themselves to handle what to do with Guard+Exit nodes.

However, because this is a mostly harmless result that just causes clients to revert to the old weights when it happens, and because a bit of work and thought is needed to decide how to properly allocate the Guard flag, we're not going to just do a quick fix and allow weights for the D=0 situation. We should fix this issue once we feel that enough clients have upgraded to 0.2.2.x for it to make sense to fix it properly.

[Automatically added by flyspray2trac: Operating System: All]

Note: See TracQuery for help on using queries.