Custom Query (15543 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 15543)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#7591 wontfix "Bug: Duplicate call to connection_mark_for_close at directory.c" tmpname0901
Description

After reading about bufferevents in the v0.2.3.25 release notes I added "--enable-bufferevents" to my Tor config. Now I intermittently get this error:

[warn] Bug: Duplicate call to connection_mark_for_close at directory.c:3571 (first at directory.c:3571)

By "intermittently" I mean I've gotten this error 19 times in the past 11 hours, logged in groups of 2 - 6 at a time.

No errors of this type are seen with v0.2.3.25 when not configuring for bufferevents.

Are bufferevents supposed to be ready for prime time, or is this still a feature in development?

#6149 wontfix "Censorship-timeline" for Tor phw
Description

It was shortly discussed on #tor-dev that some sort of "censorship-timeline" for Tor would be helpful. In particular, this should provide:

  • Detailed technical analyses of the censorship mechanisms in place (DPI fingerprints and manufacturers, traceroutes, ...)
  • Code and data to reproduce all experiments
  • Tor patches and standalone tools to evade the censorship devices

After all, this timeline should serve as a comprehensive archive for all people interested in how Tor is getting blocked. It should make it easy to answer questions such as "What happened to Tor in country X back in Y?".

There are also some open questions:

  • How should the data be structured? In form of a timeline? Or country based? Something else?
  • What data should be published and when? Full disclosure too early in the process helps the censors.
  • How should it be presented? In a wiki page or a standalone web site?
#2008 duplicate "Circuit Build Times Network Close" warnings xebulba
Description

Oct 04 11:36:31.905 [Warning] circuit_build_times_network_close(): Bug: Circuit somehow completed a hop while the network was not live. Network was last live at 2010-10-04 11:35:30, but circuit launched at 2010-10-04 11:35:30. It's now 2010-10-04 11:36:31.

Oct 04 12:06:13.958 [Warning] circuit_build_times_network_close(): Bug: Circuit somehow completed a hop while the network was not live. Network was last live at 2010-10-04 12:05:12, but circuit launched at 2010-10-04 12:05:12. It's now 2010-10-04 12:06:13.

[]

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.