Re: [tor-bugs] #12849 [Tor Sysadmin Team]: Add web cache to Onionoo's setup
#12849: Add web cache to Onionoo's setup ---+- Reporter: karsten| Owner: Type: task | Status: new Priority: normal | Milestone: Component: Tor Sysadmin Team |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | ---+- Comment (by weasel): Can you start by adding proper Cache-Control headers to the application's output? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12849#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12850 [Tor Browser]: Tor unexpectedly exit
#12850: Tor unexpectedly exit -+--- Reporter: mttp | Owner: tbb-team Type: defect | Status: new Priority: normal | Milestone: Component: Tor Browser |Version: Resolution: | Keywords: tbb-helpdesk-frequent Actual Points: | Parent ID: Points: | -+--- Comment (by cypherpunks): the browser works only a minute or so after that i get an error which says the browser has exited. after that i cant load any sites It's a little confusing, what application terminated, Tor or browser? What generated message box about application exited? If Windows OS then what details it reports yet? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12850#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12849 [Tor Sysadmin Team]: Add web cache to Onionoo's setup
#12849: Add web cache to Onionoo's setup
---+-
Reporter: karsten| Owner:
Type: task | Status: new
Priority: normal | Milestone:
Component: Tor Sysadmin Team |Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
---+-
Comment (by karsten):
Certainly. Added the following header. Does this work?
{{{
Cache-Control: public,max-age=300
}}}
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/12849#comment:2
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12853 [Tor Sysadmin Team]: Replace OpenPGP key 0x4814DEC22B307C3C by 0x8382C95C29023DF9
#12853: Replace OpenPGP key 0x4814DEC22B307C3C by 0x8382C95C29023DF9
---+-
Reporter: lunar | Owner:
Type: task | Status: new
Priority: normal | Milestone:
Component: Tor Sysadmin Team |Version:
Keywords: | Actual Points:
Parent ID: | Points:
---+-
{{{
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please replace my old key, 0x4814DEC22B307C3C:
pub 4096R/4814DEC22B307C3C 2009-07-09 [expires: 2015-05-01]
Key fingerprint = ECF2 DEA8 9EB9 0C61 2440 B2B8 4814 DEC2 2B30 7C3C
uid Jérémy Bobbio lu...@debian.org
uid Jérémy Bobbio jeremy.bob...@irq7.fr
uid Lunar lu...@torproject.org
sub 4096R/9953C968306334A8 2009-07-09 [expires: 2015-05-01]
with the new key, 0x8382C95C29023DF9:
pub 4096R/8382C95C29023DF9 2014-05-30 [expires: 2014-11-26]
Key fingerprint = 0603 CCFD 9186 5C17 E88D 4C79 8382 C95C 2902 3DF9
uid Lunar lu...@anargeek.net
uid Jérémy Bobbio jeremy.bob...@irq7.fr
uid Lunar lu...@torproject.org
uid Jérémy Bobbio lu...@debian.org
sub 4096R/402C22503D36E936 2014-05-30
sub 4096R/A5ED00CE24291162 2014-05-30
sub 4096R/512BAE1CC2EEB69E 2014-05-30
I am switching to a new offline master key.
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJT6ynxAAoJEEgU3sIrMHw8LzUQAK1HRQ/kl5ba2goOw/3z4XQv
iYC/p9UWr2V3WCktLThYNiVM+cAcEwRLAOpKHm+dM/FBoT9JElj/1nskXIadLx+g
YOGQikWHYQYs7rtefIISRX3m4kFrdzEebVrHe13I978QHY3RV1EbwL+KlC/aXcv9
XOVE9QZidTwT0J8pJfh0jjPLVos6kRxwQxGJzzSVwKsViu3UqM+orfHdwhVoPAkg
TW9UG0j4ySJG02COzX7k3Lif0pp3wxh1cJ31eenIqmxU03Mfx9lYHZkxqK3+zMEj
1ocbsIq0x5c3G0fWnLcUkXt3u7Bo9xNHbnJkU7S0tvz6kMfEl8I6QNlZLGdwQbty
pOWLKwlM3KFqJRgf5ZZp92Jj9h2wViz6W00lkf8gFnDxWKhvGzQpDNbDV+pTtcvo
cGEorH9S469zdRHJ2xzErHh3jZdIiugAsDVPzE6K80N3yx6zg2dSna4P5V2HiITw
ddPEsGmeob1q2XPR3FAomC9fO0A3mxii8uPM0o4DJZnjwMnLJW0yedHedgDea4QE
mVomGpwQNmvFtO+IE4GlRtOpusl9JaLhMxuJbY4pU56CbRQN0/nA8UNzIe37Sioi
pzeeO62F2+OZ8ZdyaunNc+qCVpzWFotwhd2PeXMMI1vZMS/0obpNk8vHieX23xMt
eRlmlmEjqPQ3YVO+Ut8t
=QubU
-END PGP SIGNATURE-
}}}
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/12853
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12849 [Tor Sysadmin Team]: Add web cache to Onionoo's setup
#12849: Add web cache to Onionoo's setup ---+- Reporter: karsten| Owner: Type: task | Status: new Priority: normal | Milestone: Component: Tor Sysadmin Team |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | ---+- Comment (by weasel): I have enabled and configured Apache's mod_mem_cache. Note that this is per apache process, and not shared across workers. Is that already good enough, or should we investigate something more complex? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12849#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12732 [Onionoo]: an onionoo java cli is available
#12732: an onionoo java cli is available -+- Reporter: iwakeh | Owner: Type: project | Status: new Priority: minor| Milestone: Component: Onionoo |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+- Comment (by karsten): Yes, you're right. Switched to the j7master branch, looks good. I suggest making that the default master branch to reduce this source of confusion. I also had the opportunity to test it a bit, and it looks like a useful tool. Want me to add it to the list of [https://onionoo.torproject.org known Onionoo clients]? That list is mostly for developers to get inspired what tools they could hack on. How would you describe your tool in one sentence? If you want to announce your tool more broadly, I suggest subscribing to the tor-talk@ mailing list and posting an announcement there. And do you want me to inform you of major Onionoo protocol changes? If yes, I'll need your email address. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12732#comment:9 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12850 [Tor Browser]: Tor unexpectedly exit
#12850: Tor unexpectedly exit -+--- Reporter: mttp | Owner: tbb-team Type: defect | Status: new Priority: normal | Milestone: Component: Tor Browser |Version: Resolution: | Keywords: tbb-helpdesk-frequent Actual Points: | Parent ID: Points: | -+--- Comment (by mttp): Replying to [comment:1 mcs]: What version of TB is being used? My understanding is this happened after a new install from a new download, so 3.6.3. Is that the complete tor log that was available via Tor Launcher's Copy To Clipboard command? I am surprised it does not include a Bootstrapped 100% message. This is the entirity of the log that I was given. Is this really a tbb-helpdesk-frequent issue? To me that implies that this same behavior is being encountered by several TB users (Tor unexpectedly exits after one minute). I use this tag if the issue is not an isolated one-user occurrence. If the reporter of this issue can reproduce the problem repeatedly, it probably makes sense to have them send us a copy of their torrc file and also have them collect a tor debug log. I've told the user about this ticket, but I'll also ask for more information over RT. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12850#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #6456 [Tor]: Merge parse_client_transport_line() and parse_server_transport_line()
#6456: Merge parse_client_transport_line() and parse_server_transport_line() -+- Reporter: asn | Owner: andrea Type: defect | Status: needs_revision Priority: trivial | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: pt refactor tor-bridge Actual Points: | 026-triaged-1 026-deferrable Points: | Parent ID: -+- Changes (by nickm): * status: needs_review = needs_revision -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/6456#comment:11 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #6456 [Tor]: Merge parse_client_transport_line() and parse_server_transport_line()
#6456: Merge parse_client_transport_line() and parse_server_transport_line()
-+-
Reporter: asn | Owner: andrea
Type: defect | Status: needs_review
Priority: trivial | Milestone: Tor: 0.2.6.x-final
Component: Tor |Version:
Resolution: | Keywords: pt refactor tor-bridge
Actual Points: | 026-triaged-1 026-deferrable
Points: | Parent ID:
-+-
Comment (by nickm):
{{{
09:44 nickm ok. quick suggestion before merge: The uhnit tests should
make
sure that the arguments to the mock functions have the
right
values, I think.
09:44 nickm else the functions could pass the tests without actually
parsing
the transport lines correctly
}}}
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/6456#comment:10
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12854 [Tor]: Update to August GeoIP2 database
#12854: Update to August GeoIP2 database --+- Reporter: karsten | Owner: Type: enhancement | Status: new Priority: normal| Milestone: Component: Tor |Version: Keywords: tor-client tor-relay | Actual Points: Parent ID:| Points: --+- [https://gitweb.torproject.org/karsten/tor.git/shortlog/refs/heads/geoip- aug2014 geoip-aug2014] contains the updated geoip file with IPv4 ranges and is supposed to be merged into maint-0.2.3. [https://gitweb.torproject.org/karsten/tor.git/shortlog/refs/heads/geoip6-aug2014 geoip6-aug2014] contains the updated geoip6 file with IPv6 ranges and is supposed to be merged into maint-0.2.4 (the first maint-* branch that contains a geoip6 file). -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12854 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12855 [Tor]: Use calloc and reallocarray instead of malloc(a*b), malloc_zero(a*b), or realloc(p, a*b)
#12855: Use calloc and reallocarray instead of malloc(a*b), malloc_zero(a*b), or realloc(p,a*b) ---+ Reporter: nickm | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor|Version: Keywords: tor-relay | Actual Points: Parent ID: | Points: ---+ It's stupid and error-prone to multiply-then-malloc: you're just begging for an integer overflow. We should add a reallocarray (like OpenBSD uses) and use spatch/coccinelle to replace all our bad allocations. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12855 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12855 [Tor]: Use calloc and reallocarray instead of malloc(a*b), malloc_zero(a*b), or realloc(p, a*b)
#12855: Use calloc and reallocarray instead of malloc(a*b), malloc_zero(a*b), or realloc(p,a*b) + Reporter: nickm | Owner: Type: defect | Status: needs_review Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-relay Actual Points: | Parent ID: Points: | + Changes (by nickm): * status: new = needs_review Comment: That was fast. See branch use_calloc in my public repository. I think this is for 0.2.6. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12855#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12849 [Tor Sysadmin Team]: Add web cache to Onionoo's setup
#12849: Add web cache to Onionoo's setup ---+- Reporter: karsten| Owner: Type: task | Status: new Priority: normal | Milestone: Component: Tor Sysadmin Team |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | ---+- Comment (by karsten): You said on IRC that you switched to disk cache, which I think makes sense. I tweaked the cache-control logic to set `max-age` to values between 5 and 40 minutes. Right now I'm seeing 80% cache hits, which is pretty good. Let's look again in a day or so, but I'm optimistic. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12849#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #6761 [Tor]: PDS_NO_EXISTING_SERVERDESC_FETCH is somewhat archaic
#6761: PDS_NO_EXISTING_SERVERDESC_FETCH is somewhat archaic -+- Reporter: arma | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-relay 026-triaged-1 Actual Points: | 026-deferrable Points: | Parent ID: -+- Changes (by andrea): * keywords: tor-relay = tor-relay 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/6761#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #6852 [Tor]: bridges (especially unpublished ones) should include usage info in their heartbeats
#6852: bridges (especially unpublished ones) should include usage info in their heartbeats ---+--- Reporter: arma | Owner: Type: | Status: needs_revision enhancement | Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor| Keywords: tor-bridge SponsorJ 026-triaged-1 Resolution: | Parent ID: Actual Points: | Points: | ---+--- Changes (by nickm): * status: new = needs_revision * keywords: tor-bridge SponsorJ = tor-bridge SponsorJ 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/6852#comment:11 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #6852 [Tor]: bridges (especially unpublished ones) should include usage info in their heartbeats
#6852: bridges (especially unpublished ones) should include usage info in their heartbeats ---+--- Reporter: arma | Owner: Type: | Status: needs_revision enhancement | Milestone: Tor: 0.2.??? Priority: normal |Version: Component: Tor| Keywords: tor-bridge SponsorJ 026-triaged-1 Resolution: | Parent ID: Actual Points: | Points: | ---+--- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/6852#comment:12 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #6852 [Tor]: bridges (especially unpublished ones) should include usage info in their heartbeats
#6852: bridges (especially unpublished ones) should include usage info in their heartbeats ---+--- Reporter: arma | Owner: Type: | Status: needs_revision enhancement | Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor| Keywords: tor-bridge SponsorJ 026-triaged-1 Resolution: | Parent ID: Actual Points: | Points: | ---+--- Changes (by nickm): * milestone: Tor: 0.2.??? = Tor: 0.2.6.x-final -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/6852#comment:13 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #7899 [Tor]: We forget to set tls_error sometimes
#7899: We forget to set tls_error sometimes -+- Reporter: asn | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-client tls controller Actual Points: | 026-triaged-1 026-deferrabled Points: | Parent ID: -+- Changes (by nickm): * keywords: tor-client tls controller = tor-client tls controller 026-triaged-1 026-deferrabled -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/7899#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down
#8001: obfsproxy makes tor warn when one bridge is down +-- Reporter: arma| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: tor-client Actual Points: | Parent ID: Points: | +-- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/8001#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #8093 [Tor]: Jan 29 23:32:20.066 [Warning] Bug/attack: unexpected sendme cell from client. Closing circ.
#8093: Jan 29 23:32:20.066 [Warning] Bug/attack: unexpected sendme cell from client. Closing circ. -+- Reporter: | Owner: nickm Gravitas | Status: new Type: defect | Milestone: Tor: 0.2.??? Priority: normal |Version: Tor: 0.2.4.9-alpha Component: Tor | Keywords: tor-client, 025-triaged needs- Resolution: | insight Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-client, 025-triaged = tor-client, 025-triaged needs- insight * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/8093#comment:31 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #8239 [Tor]: Hidden services should try harder to reuse their old intro points
#8239: Hidden services should try harder to reuse their old intro points -+-- Reporter: arma | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-hs 026-triaged-1 Actual Points: | Parent ID: Points: | -+-- Changes (by nickm): * keywords: tor-hs = tor-hs 026-triaged-1 Comment: See also https://lists.torproject.org/pipermail/tor- dev/2014-August/007335.html -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/8239#comment:5 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #8243 [Tor]: Getting the HSDir flag should require more effort
#8243: Getting the HSDir flag should require more effort -+- Reporter: arma | Owner: Type: | Status: new enhancement| Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor | Keywords: tor-auth needs-proposal Resolution: | 026-triaged-1 Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-auth needs-proposal = tor-auth needs-proposal 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/8243#comment:10 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #7478 [Tor]: Allow routersets to include/exclude nodes by IPv6 address (was: routerset membership tests should consider nodes' addr6 fields)
#7478: Allow routersets to include/exclude nodes by IPv6 address -+- Reporter: nickm| Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: tor-client ipv6 Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/7478#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #8546 [Tor]: Make a copy-able connection-config type to limit copy burden of isolation flags, etc
#8546: Make a copy-able connection-config type to limit copy burden of isolation flags, etc -+- Reporter: nickm| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-client refactoring easy Actual Points: | 026-triaged-1 026-deferrable Points: | Parent ID: -+- Changes (by nickm): * keywords: tor-client refactoring easy = tor-client refactoring easy 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/8546#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #8625 [Tor]: Do not call networkstatus_reset_download_failures() hourly
#8625: Do not call networkstatus_reset_download_failures() hourly -+- Reporter: nickm| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-client 025-backport Actual Points: | 026-triaged-1 026-deferrable Points: | Parent ID: -+- Changes (by nickm): * keywords: tor-client 024-backport = tor-client 025-backport 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/8625#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #8786 [Tor]: Add extra-info line that tracks the number of consensus downloads of each pluggable transports
#8786: Add extra-info line that tracks the number of consensus downloads of each pluggable transports -+- Reporter: asn | Owner: Type: | Status: new enhancement| Milestone: Tor: 0.2.6.x-final Priority: minor|Version: Component: Tor | Keywords: pt tor-bridge flashproxy Resolution: | 026-triaged-1 026-deferrable Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * priority: normal = minor * keywords: pt tor-bridge flashproxy = pt tor-bridge flashproxy 026-triaged-1 026-deferrable * type: defect = enhancement -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/8786#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #9067 [Tor]: Choice of address and match of fascist_firewall_allows_address* need to consider ipv6
#9067: Choice of address and match of fascist_firewall_allows_address* need to consider ipv6 +- Reporter: nickm | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: tor-client, 025-triaged Actual Points: | Parent ID: #6027 Points: | +- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9067#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #9498 [Tor]: Allow bridge descriptors to contain no address if they are not being published
#9498: Allow bridge descriptors to contain no address if they are not being published -+- Reporter: nwf | Owner: Type: | Status: new enhancement| Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Tor: unspecified Component: Tor | Keywords: tor-bridge need-spec bridgedb Resolution: | needs-proposal 026-triaged-1 026-deferrable Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-bridge,need-spec,bridgedb = tor-bridge need-spec bridgedb needs-proposal 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9498#comment:12 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #9580 [Tor]: Tor should accept combined pluggable transport names
#9580: Tor should accept combined pluggable transport names -+- Reporter: asn | Owner: Type: | Status: new enhancement| Milestone: Tor: 0.2.6.x-final Priority: minor|Version: Component: Tor | Keywords: tor-pt 025-backport needs-spec easy Resolution: | 026-triaged-1 026-deferrable Actual Points: | Parent ID: #10061 Points: | -+- Changes (by nickm): * keywords: tor-pt 025-backport needs-spec = tor-pt 025-backport needs- spec easy 026-triaged-1 026-deferrable * priority: normal = minor * type: defect = enhancement -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9580#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10476 [Tor]: Reattach non open streams if circuit destroyed
#10476: Reattach non open streams if circuit destroyed -+-- Reporter: cypherpunks | Owner: Type: enhancement | Status: new Priority: major| Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: tor-client Actual Points: | Parent ID: Points: | -+-- Changes (by nickm): * priority: normal = major * keywords: 024-backport tor-client = tor-client * type: defect = enhancement * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10476#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #9819 [Tor]: Circuits through entry guards aren't distinguished on whether they originated locally
#9819: Circuits through entry guards aren't distinguished on whether they originated locally +- Reporter: andrea | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: 0.2.4.17-rc Resolution: | Keywords: tor-relay 026-triaged-1 Actual Points: | Parent ID: Points: | +- Changes (by nickm): * keywords: = tor-relay 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9819#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11138 [Tor]: Improve code handling SOCKS connection in tor daemon
#11138: Improve code handling SOCKS connection in tor daemon -+- Reporter: dgoulet | Owner: Type: | Status: new enhancement| Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor | Keywords: 026-triaged-1 026-deferrable Resolution: | trunnel tor-client Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: = 026-triaged-1 026-deferrable trunnel tor-client -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11138#comment:7 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10816 [Tor]: Don't exclude NTE_BAD_KEYSET error for windows
#10816: Don't exclude NTE_BAD_KEYSET error for windows -+- Reporter: | Owner: cypherpunks| Status: new Type: defect | Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor | Keywords: tor-client windows crypto Resolution: | 026-triaged-1 Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-client windows crypto = tor-client windows crypto 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10816#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12463 [Tor]: Missing ciphersuite in tor spec
#12463: Missing ciphersuite in tor spec -+ Reporter: cypherpunks | Owner: Type: defect | Status: new Priority: minor| Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: spec Actual Points: | Parent ID: Points: | -+ Comment (by nickm): I don't think that's a contradiction; they MUST/SHOULD support those, and MAY support others. Is there a way to state this more clearly? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12463#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #9635 [Tor]: Tor clients warn when they use the wrong ntor onion key
#9635: Tor clients warn when they use the wrong ntor onion key -+- Reporter: bastik | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: unspecified Resolution: | Keywords: tor-bridge 026-triaged-1 Actual Points: | 025-backport Points: | Parent ID: -+- Changes (by nickm): * keywords: tor-bridge 024-backport 025-triaged = tor-bridge 026-triaged-1 025-backport -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9635#comment:17 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #9775 [Tor]: Authorities should report when they don't vote Running but some addresses are still reachable
#9775: Authorities should report when they don't vote Running but some addresses are still reachable -+ Reporter: arma | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-auth 026-triaged-1 Actual Points: | Parent ID: Points: | -+ Changes (by nickm): * keywords: tor-auth = tor-auth 026-triaged-1 * type: defect = enhancement -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9775#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10067 [Tor]: Have `reject *` as the default exit policy
#10067: Have `reject *` as the default exit policy -+ Reporter: lunar| Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-relay 026 Actual Points: | Parent ID: Points: | -+ Changes (by nickm): * keywords: tor-relay = tor-relay 026 Comment: if ExitNode is 'auto' and you are a relay and have no exit policy set, then we behave as currently, but warn you that you are being an exit node, and you should set ExitNode 1 or 0. In a later version, we make ExitNode off by default. This still seems smart. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10067#comment:12 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10837 [Tor]: Stop giving out version 2 descriptors to controllers
#10837: Stop giving out version 2 descriptors to controllers -+-- Reporter: karsten | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+-- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10837#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10922 [Tor]: tor connected to bwauth produces lots of pathbias_count_use_attempt BUG messages
#10922: tor connected to bwauth produces lots of pathbias_count_use_attempt BUG messages -+- Reporter: | Owner: Sebastian | Status: needs_information Type: defect | Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Tor: 0.2.4.20 Component: Tor | Keywords: tor-client bwauth 026-triaged-1 Resolution: | regression Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-client bwauth 024-backport regression = tor-client bwauth 026-triaged-1 regression * status: new = needs_information -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10922#comment:5 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10957 [Tor]: Be more aggressive about enabling Extended ORPort
#10957: Be more aggressive about enabling Extended ORPort -+- Reporter: asn | Owner: Type: task | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-pt, tor-bridge needs-design Actual Points: | 026-triaged-1 026-deferrable Points: | Parent ID: -+- Changes (by nickm): * keywords: tor-pt, tor-bridge = tor-pt, tor-bridge needs-design 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10957#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11101 [Tor]: Bridges should report implementation versions of their pluggable transports
#11101: Bridges should report implementation versions of their pluggable transports -+- Reporter: arma | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: bridgedb needs-proposal Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: bridgedb = bridgedb needs-proposal * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11101#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11119 [Tor]: Write a proposal for client-side key pinning
#9: Write a proposal for client-side key pinning -+- Reporter: nickm| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-client needs-proposal Actual Points: | 026-triaged-1 Points: | Parent ID: -+- Changes (by nickm): * keywords: tor-client needs-proposal = tor-client needs-proposal 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11243 [Tor]: Don't fetch any descriptor which we already fetched and found to be ill-formed
#11243: Don't fetch any descriptor which we already fetched and found to be ill- formed +- Reporter: nickm | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-relay 026-triaged-1 Actual Points: | Parent ID: Points: | +- Changes (by nickm): * keywords: tor-relay = tor-relay 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11243#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12693 [Tor]: autoreconf 2.62 can't handle AS_VAR_IF in our configure.ac
#12693: autoreconf 2.62 can't handle AS_VAR_IF in our configure.ac + Reporter: arma| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: 0.2.5.2-alpha Resolution: | Keywords: tor 026-triaged-1 025-backport Actual Points: | Parent ID: Points: | + Changes (by nickm): * keywords: = tor 026-triaged-1 025-backport Comment: The easy workaround here is an m4_ifdef. See branch bug12693_025 in my public repository. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12693#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11327 [Tor]: Dir auths should choose Fast and Guard flags by consensus weight if they don't measure
#11327: Dir auths should choose Fast and Guard flags by consensus weight if they don't measure + Reporter: arma| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-auth 026-triaged-1 Actual Points: | Parent ID: Points: | + Changes (by nickm): * keywords: tor-auth = tor-auth 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11327#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10922 [Tor]: tor connected to bwauth produces lots of pathbias_count_use_attempt BUG messages
#10922: tor connected to bwauth produces lots of pathbias_count_use_attempt BUG messages -+- Reporter: | Owner: Sebastian | Status: needs_information Type: defect | Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Tor: 0.2.4.20 Component: Tor | Keywords: tor-client bwauth 026-triaged-1 Resolution: | regression Actual Points: | Parent ID: Points: | -+- Comment (by Sebastian): What kind of information does this need? Did you flag it as such because you don't want to have to look at it, and someone else should? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10922#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #10067 [Tor]: Have `reject *` as the default exit policy
#10067: Have `reject *` as the default exit policy -+- Reporter: lunar| Owner: Type: | Status: new enhancement| Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor | Keywords: tor-relay 026-triaged-1 Resolution: | 026-deferrable Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-relay 026 = tor-relay 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/10067#comment:13 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11328 [Tor]: Dir auths should compute Guard WFU using the consensus, not private history
#11328: Dir auths should compute Guard WFU using the consensus, not private history + Reporter: arma| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-auth 026-triaged-1 Actual Points: | Parent ID: Points: | + Changes (by nickm): * keywords: tor-auth = tor-auth 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11328#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11338 [Tor]: Allow hostnames in bridge configuration lines when used with PTs
#11338: Allow hostnames in bridge configuration lines when used with PTs -+--- Reporter: nickm| Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: tor-client pt Actual Points: | Parent ID: Points: | -+--- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11338#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11397 [Tor]: Building circuits blocks new connections
#11397: Building circuits blocks new connections
-+--
Reporter: evandro | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: 0.2.???
Component: Tor |Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-+--
Changes (by nickm):
* milestone: Tor: 0.2.6.x-final = Tor: 0.2.???
Comment:
{{{
12:11 athena slightly worried about a change that makes us potentially
use
an old circuit forever if the firewall starts blocking
*all*
new connections
12:11 athena *maybe* it'd be okay if we introduced soft and hard
timeouts
for circuits
12:11 @nickm with single-guard, you should pretty much always have a
good
connection though.
12:12 athena i.e., older than the soft timeout means new connection
triggers
building a new circuit and uses the old if it takes too
long
12:12 athena hard blocks new connections until a fresh circuit is
available
12:12 athena hmmm
12:12 athena (we still might have multiple guards if the user changes
the
config setting manually, though, IIUC)
12:13 @nickm that's true, but I'm not sure how much time we should spend
optimizing for people behind fascist firewalls who also use
non-default guard settings
12:13 @nickm also, we are supposed to be building circuits preemptively,
and
using them preemptively. So for most people, this
shouldn't be
a problem.
12:13 athena also, with single guard, when we build a new circuit, do
we use
the existing channel to the guard to do it, or open a
whole new
channel?
12:13 athena the former, i think
12:13 @nickm we use the existing channel
12:14 @nickm I say that I should copy-and-paste most of this discussion,
and
put the ticket in ???
12:14 athena yeah
}}}
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/11397#comment:2
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11397 [Tor]: Keep using too-dirty circuits if no new circuit can be built? (was: Building circuits blocks new connections)
#11397: Keep using too-dirty circuits if no new circuit can be built? -+-- Reporter: evandro | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+-- -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11397#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11454 [Tor]: If two auth certs are both old but were generated nearby in time, we keep both
#11454: If two auth certs are both old but were generated nearby in time, we keep both + Reporter: arma| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: 026-triaged-1 Actual Points: | Parent ID: Points: | + Changes (by nickm): * keywords: = 026-triaged-1 Comment: I think what we want here is for the logic to be discard superseded certificates if any certificate newer than them has existed for at least X days? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11454#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11598 [Tor]: Investigate using of TLSv1_method instead of SSLv23_method
#11598: Investigate using of TLSv1_method instead of SSLv23_method
-+
Reporter: cypherpunks | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.6.x-final
Component: Tor |Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-+
Comment (by nickm):
From the manpage:
{{{
TLSv1_method(void), TLSv1_server_method(void),
TLSv1_client_method(void)
A TLS/SSL connection established with these methods will only
understand the TLSv1 protocol. A client will send out TLSv1
client
hello messages and will indicate that it only understands
TLSv1. A
server will only understand TLSv1 client hello messages. This
especially means, that it will not understand SSLv2 client
hello
messages which are widely used for compatibility reasons, see
SSLv23_*_method(). It will also not understand SSLv3 client
hello
messages.
SSLv23_method(void), SSLv23_server_method(void),
SSLv23_client_method(void)
A TLS/SSL connection established with these methods will
understand
the SSLv2, SSLv3, and TLSv1 protocol. A client will send out
SSLv2
client hello messages and will indicate that it also
understands
SSLv3 and TLSv1. A server will understand SSLv2, SSLv3, and
TLSv1
client hello messages. This is the best choice when
compatibility
is a concern.
}}}
If existing clients are sending out the old ClientHello types, we can't
demand TLS 1.0. But does disabling SSL2 and SSL3 make it send a TLS1
clienthello? Somebody needs to look at the openssl code (ick) this to see
what clients are actually sending.
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/11598#comment:3
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11598 [Tor]: Investigate using of TLSv1_method instead of SSLv23_method
#11598: Investigate using of TLSv1_method instead of SSLv23_method -+-- Reporter: cypherpunks | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+-- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11598#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11679 [Tor]: Download status for consensus scheduled as generic
#11679: Download status for consensus scheduled as generic -+- Reporter: cypherpunks | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-client easy 026-triaged Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-client = tor-client easy 026-triaged -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11679#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12856 [HTTPS Everywhere: Chrome]: avast! Online Security plug-in conflict with HTTPS Anywhere (Chrome)
#12856: avast! Online Security plug-in conflict with HTTPS Anywhere (Chrome) --+-- Reporter: cypherpunks | Owner: zyan Type: defect| Status: new Priority: normal| Milestone: Component: HTTPS Everywhere: Chrome |Version: Keywords:| Actual Points: Parent ID:| Points: --+-- I recently installed the avast! Online Security plug-in for Chrome, and have noticed a periodic Extension error alert. The details provided by Chrome in my plug-in list, under HTTPS Anywhere (2014.6.26) are: Warning: This extension failed to redirect a network request to https://www.google-analytics.com/ga.js because another extension (avast! Online Security) redirected it to chrome- extension://gomekmidlodglbbmalcneegieacbdmki/common/mocks/ga.js. I have Web Tracking blocked enabled in my avast! settings, and was told by avast tech support to either disable this feature or disable HTTPS Anywhere. Is it possible to add an exception so I can both block analytics with avast and continue to use HTTPS Anywhere without constantly throwing up an error? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12856 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11737 [Tor]: Damage of cached hte_hash values for HTs leads to undefined behavior
#11737: Damage of cached hte_hash values for HTs leads to undefined behavior -+- Reporter: | Owner: cypherpunks| Status: new Type: defect | Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor | Keywords: tor-relay 026-triaged-1 Resolution: | 026-deferrable Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-relay = tor-relay 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11737#comment:11 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12062 [Tor]: Audit DisableNetwork, we_are_hibernating usage
#12062: Audit DisableNetwork, we_are_hibernating usage +-- Reporter: nickm | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-client 026-triaged-1 Actual Points: | Parent ID: Points: | +-- Changes (by nickm): * keywords: tor-client = tor-client 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12062#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12226 [Tor]: Make Strict{Entry, Exit}Nodes obsolete, rather than synonym for StrictNodes?
#12226: Make Strict{Entry,Exit}Nodes obsolete, rather than synonym for
StrictNodes?
+---
Reporter: arma| Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.6.x-final
Component: Tor |Version:
Resolution: | Keywords: tor-client 026-triaged-1 easy
Actual Points: | Parent ID:
Points: |
+---
Changes (by nickm):
* keywords: = tor-client 026-triaged-1 easy
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/12226#comment:1
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12138 [Tor]: No IPv6 support when suggesting a bindaddr to a PT
#12138: No IPv6 support when suggesting a bindaddr to a PT -+- Reporter: asn | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-pt tor-bridge 026-triaged-1 Actual Points: | 026-deferrable Points: | Parent ID: -+- Changes (by nickm): * keywords: tor-pt tor-bridge = tor-pt tor-bridge 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12138#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12464 [Tor]: When Tor 0.2.6.x is closer to done, profile relays running Tor 0.2.6.x and optimize accordingly
#12464: When Tor 0.2.6.x is closer to done, profile relays running Tor 0.2.6.x and optimize accordingly +- Reporter: nickm | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-relay performance 026-triaged-1 Actual Points: | Parent ID: Points: | +- Changes (by nickm): * keywords: tor-relay performance = tor-relay performance 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12464#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11679 [Tor]: Download status for consensus scheduled as generic
#11679: Download status for consensus scheduled as generic -+--- Reporter: cypherpunks | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-client easy 026-triaged-1 Actual Points: | Parent ID: Points: | -+--- Changes (by nickm): * keywords: tor-client easy 026-triaged = tor-client easy 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11679#comment:4 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] [Tor Bug Tracker Wiki] Batch modify: #12466, #12595, #12598, #12485
Batch modification to #12466, #12595, #12598, #12485 by nickm: keywords to 026-triaged-1 -- Tickets URL: https://trac.torproject.org/projects/tor/query?id=12466%2C12595%2C12598%2C12485 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12399 [Tor]: Hash of session info was not as expected
#12399: Hash of session info was not as expected +-- Reporter: ln5 | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Resolution: | Keywords: 025-backport Actual Points: | Parent ID: Points: | +-- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12399#comment:5 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12442 [Tor]: Bridges should put their transport lines in their main descriptor, not extra-info desc
#12442: Bridges should put their transport lines in their main descriptor, not extra-info desc -+- Reporter: arma | Owner: Type: | Status: new enhancement| Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Component: Tor | Keywords: tor-bridge, maybe-proposal, Resolution: | bridgedb-parsers 026-triaged-1 026-deferrable Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-bridge, maybe-proposal, bridgedb-parsers = tor-bridge, maybe-proposal, bridgedb-parsers 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12442#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12463 [Tor]: Missing ciphersuite in tor spec
#12463: Missing ciphersuite in tor spec -+ Reporter: cypherpunks | Owner: Type: defect | Status: new Priority: minor| Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: spec 026-triaged-1 Actual Points: | Parent ID: Points: | -+ Changes (by nickm): * keywords: spec = spec 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12463#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12854 [Tor]: Update to August GeoIP2 database
#12854: Update to August GeoIP2 database --+ Reporter: karsten | Owner: Type:| Status: closed enhancement | Milestone: Tor: 0.2.6.x-final Priority: normal|Version: Component: Tor | Keywords: tor-client tor-relay 026-triaged-1 Resolution:| Parent ID: implemented | Actual Points:| Points:| --+ Changes (by nickm): * status: needs_review = closed * resolution: = implemented Comment: Merged; thanks! -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12854#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12377 [Tor]: get_interface_address6() behaviour iff all interface addresses are internal
#12377: get_interface_address6() behaviour iff all interface addresses are internal -+- Reporter: rl1987 | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: unspecified Resolution: | Keywords: tor-relay 026-triaged-1 Actual Points: | 026-deferrable Points: | Parent ID: #12376 -+- Changes (by nickm): * keywords: = tor-relay 026-triaged-1 026-deferrable -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12377#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12478 [Tor]: Ownership error on hidden service dir encountered on config reload kills Tor process
#12478: Ownership error on hidden service dir encountered on config reload kills Tor process +--- Reporter: andrea | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.??? Component: Tor |Version: Tor: 0.2.4.20 Resolution: | Keywords: Actual Points: | Parent ID: Points: | +--- Changes (by nickm): * milestone: Tor: 0.2.6.x-final = Tor: 0.2.??? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12478#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12509 [Tor]: Setting an option clears addressmappings, automapped addresses
#12509: Setting an option clears addressmappings, automapped addresses -+- Reporter: epoch| Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: 0.2.5.5-alpha Resolution: | Keywords: Automapping, dnsport, Actual Points: | cookieauthenticataion, 025-backport Points: | 026-triaged-1 | Parent ID: -+- Changes (by nickm): * keywords: Automapping, dnsport, cookieauthenticataion, 025-backport = Automapping, dnsport, cookieauthenticataion, 025-backport 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12509#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12538 [Tor]: A relay is automatically a dir cache
#12538: A relay is automatically a dir cache -+- Reporter: | Owner: cypherpunks| Status: new Type: task | Milestone: Tor: 0.2.6.x-final Priority: normal |Version: Tor: unspecified Component: Tor | Keywords: tor-guard, tor-relay, needs- Resolution: | proposal 026-triaged-1 Actual Points: | Parent ID: Points: | -+- Changes (by nickm): * keywords: tor-guard, tor-relay, needs-proposal = tor-guard, tor-relay, needs-proposal 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12538#comment:9 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12541 [Tor]: Integrate KIST socket/circuit scheduling
#12541: Integrate KIST socket/circuit scheduling -+- Reporter: | Owner: robgjansen | Status: new Type: | Milestone: Tor: 0.2.6.x-final enhancement|Version: Priority: normal | Keywords: performance, tcp, scheduling tor- Component: Tor | relay 026-triaged-1 Resolution: | Parent ID: Actual Points: | Points: | -+- Changes (by nickm): * keywords: performance, tcp, scheduling = performance, tcp, scheduling tor-relay 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12541#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12558 [Tor]: Tor doesn't show warning for non-reachable IPv6 OR port
#12558: Tor doesn't show warning for non-reachable IPv6 OR port +-- Reporter: anong | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: 0.2.4.22 Resolution: | Keywords: ipv6 tor-relay 026-triaged-1 Actual Points: | Parent ID: Points: | +-- Changes (by nickm): * keywords: ipv6,tor-relay = ipv6 tor-relay 026-triaged-1 Comment: At the very least we could improve the comment here. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12558#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12670 [Tor]: HiddenServicePort TARGET IPv6 address
#12670: HiddenServicePort TARGET IPv6 address
-+-
Reporter: | Owner:
grarpamp | Status: new
Type: | Milestone: Tor: 0.2.6.x-final
enhancement|Version: Tor: 0.2.4.22
Priority: normal | Keywords: tor-hs documentation easy
Component: Tor | 026-triaged-1
Resolution: | Parent ID:
Actual Points: |
Points: |
-+-
Changes (by nickm):
* keywords: = tor-hs documentation easy 026-triaged-1
Comment:
AFAIK,
{{{
hiddenserviceport 80 [::1]:80
}}}
works fine. I think this is just a documentation patch.
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/12670#comment:2
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12700 [Tor]: relay_command_to_string() doesn't know about EXTEND2 / EXTENDED2
#12700: relay_command_to_string() doesn't know about EXTEND2 / EXTENDED2 -+- Reporter: arma | Owner: Type: defect | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: tor-relay 026-triaged-1 easy Actual Points: | 025-backport 024-backport Points: | Parent ID: -+- Changes (by nickm): * keywords: = tor-relay 026-triaged-1 easy 025-backport 024-backport -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12700#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12194 [Tor]: rend_client_note_connection_attempt_ended() gets called redundantly
#12194: rend_client_note_connection_attempt_ended() gets called redundantly -+- Reporter: andrea | Owner: Type: defect | Status: new Priority: minor| Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: 0.2.5.4-alpha Resolution: | Keywords: tor-hs 026-triaged-1 026-deferrable Actual Points: | easy Points: | Parent ID: -+- Changes (by nickm): * keywords: = tor-hs 026-triaged-1 026-deferrable easy -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12194#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #11624 [Tor]: Malicious relays may be able to be assigned Exit flag without exiting anywhere
#11624: Malicious relays may be able to be assigned Exit flag without exiting anywhere + Reporter: tom | Owner: Type: defect | Status: new Priority: minor | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Tor: unspecified Resolution: | Keywords: tor-auth 026-triaged-1 Actual Points: | Parent ID: Points: | + Changes (by nickm): * keywords: = tor-auth 026-triaged-1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/11624#comment:3 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12378 [Tor]: Tor configuration policies using network CIDR syntax should clamp mask bits appropriately
#12378: Tor configuration policies using network CIDR syntax should clamp mask bits appropriately ---+ Reporter: anon | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Tor|Version: Resolution: not a bug | Keywords: config exit-policy Actual Points: | Parent ID: Points: | ---+ Comment (by tordienet): I maintain tordienet. FWIW, 224.0.0.0/3 is what I intended to express. If you only allow me to write rules that cover /8, I would have to add 32 rules to express the same thing, which seems silly. You could safely interpret 10.254.0.0/8 as 10.0.0.0/8, since they mean the same thing. But you should never change the bitmask: 10.254.0.0/8 - 10.254.0.0/16 is really not the same thing. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12378#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12849 [Tor Sysadmin Team]: Add web cache to Onionoo's setup
#12849: Add web cache to Onionoo's setup ---+ Reporter: karsten| Owner: Type: task | Status: closed Priority: normal | Milestone: Component: Tor Sysadmin Team |Version: Resolution: implemented| Keywords: Actual Points: | Parent ID: Points: | ---+ Changes (by karsten): * status: new = closed * resolution: = implemented Comment: 86% cache hits and down from 160k to 9k requests handled by Tomcat per hour. I'd say this works really well. Thanks, weasel, for implementing this so quickly! Closing. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12849#comment:5 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12855 [Tor]: Use calloc and reallocarray instead of malloc(a*b), malloc_zero(a*b), or realloc(p, a*b)
#12855: Use calloc and reallocarray instead of malloc(a*b), malloc_zero(a*b), or realloc(p,a*b) + Reporter: nickm | Owner: Type: defect | Status: closed Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: fixed | Keywords: tor-relay Actual Points: | Parent ID: Points: | + Changes (by nickm): * status: needs_review = closed * resolution: = fixed Comment: Merged after review by Sebastian. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12855#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12857 [meek]: Use streaming downloads
#12857: Use streaming downloads -+- Reporter: dcf | Owner: dcf Type: enhancement | Status: new Priority: major| Milestone: Component: meek |Version: Keywords: | Actual Points: Parent ID: | Points: -+- How meek works now is, the client reads a small chunk of data from tor (up to 64 KB) and sends it in the body of a POST request. The server receives it, reads a small chunk of data from tor (up to 64 KB), and sends it back in the response. The client doesn't make another request until it has received the response to the first one, in order to keep all the chunks of data in order. Here's what would be better. The client sends a small chunk of data. The server sends a response header and any data it has pending, and leaves the response channel open. The server can use the chunked transfer-encoding to send a body of indeterminate length. The server sends downstream data over the existing streaming response channel until it receives another request. At that point, it closes the response channel and opens up a new one (which will be the response to the just-received request). The advantages are mainly about performance: there's no client polling; there's less HTTP header overhead (see #12778); and the client can send data (send a request) whenever it feels like it, without waiting for the server's most recent response, if the underlying HTTP library supports pipelining. Psiphon has already implemented something like this. There's a bit of difficulty in that the golang HTTP server [https://code.google.com/p/go/source/browse/src/pkg/net/http/server.go?r=238ff8c01b5b8749c5bffc00e1f6f5099359f1dd#1169 doesn't notify you of new requests while you're still sending a response on the same keep-alive channel]. Their workaround (and I think it is a good one) is to put a timeout on the download streaming, so that a long response won't block upstream data forever. * https://bitbucket.org/psiphon/psiphon-circumvention-system/diff/go /meek-server/meek- server.go?diff1=0ca24558e14e772a5b0e3dfb7b166914682a8fc0diff2=692f9187147cat =meek-performance We'll need to overhaul the web browser extensions, because they currently assume requests and responses with sizes known in advance. This approach won't work with Google App Engine, because App Engine [https://developers.google.com/appengine/docs/go/requests#Go_Responses doesn't support streaming downloads]. But it should work with CloudFront. See #12428 for how to improve performance with App Engine. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12857 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12428 [meek]: Make it possible to have multiple requests and responses in flight
#12428: Make it possible to have multiple requests and responses in flight -+- Reporter: dcf | Owner: dcf Type: enhancement | Status: new Priority: normal | Milestone: Component: meek |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+- Comment (by dcf): It occurs to me that we could probably very easily implement a poor man's version of this. Just send requests whenever, and rely on what we know about how our HTTPS clients like to use a single persistent TCP connection (breaking the abstraction slightly) to keep the chunks in order. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12428#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12858 [Tor Browser]: routine bug report
#12858: routine bug report -+-- Reporter: newcombat| Owner: tbb-team Type: defect | Status: new Priority: normal | Milestone: Component: Tor Browser |Version: Keywords: | Actual Points: Parent ID: | Points: -+-- I received the following error message in the Message Log while trying to connect to nolo.com. Was asked to send it to bugs at Tor. [Tue Aug 12 13:11:04 2014] Tor Software Error - The Tor software encountered an internal bug. Please report the following error message to the Tor developers at bugs.torproject.org: microdesc_free(): Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12858 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #9321 [Tor]: Load balance right when we have higher guard rotation periods
#9321: Load balance right when we have higher guard rotation periods -+- Reporter: arma | Owner: Type: project | Status: new Priority: normal | Milestone: Tor: 0.2.6.x-final Component: Tor |Version: Resolution: | Keywords: needs-proposal, tor-auth, tor- Actual Points: | client, 026-triaged-1 Points: | Parent ID: #11480 -+- Comment (by nickm): Replying to [comment:22 asn]: [...] Then 5 minutes before the hour, little-t-tor will read the guardiness output file and consider its data when voting. This all seems plausible; can any dirauth ops comment on whether this is a reasonable thing to set up? Some notes: * Instead of downloading the latest consensus from metrics, maybe we could add little-t-tor code that would save new consensuses into a directory. This way, we don't need to download bulk from metrics, apart from during the bootstrap procedure. This seems plausible and not terribly hard. The only thing to deal with here would be getting rid of old files. (see below.) I guess you could have a KeepOldConsensuses 90 days option along with OldConsensusDir /var/xyzzy that would store the last 90 days of consensuses in some directory of your choice. * To avoid keeping old summary/consensus files around that take over disk space, I added some optional cleanup switches to the scripts. Specifically, the `summizer.py` script can delete the consensus files that got summarized and can also delete consensus files older than 3 months (or N months). Similarly, the `guardiness.py` script can delete summary files older than 3 months (or N months). The idea is that every time the cron job triggers, the `summizer.py` and `guardiness.py` scripts will auto- delete the oldest summary/consensus file, keeping in disk only the useful files. This also seems plausible. Except instead of deleting the oldest unconditionally, it's probably best for them to delete any consensus whose valid-until time is more than N days before the current time. That way, if you have to re-run them, or if you mess up mtimes on your disk, they don't wind up deleting things they shouldn't. (Do you have more questions? If so, please make sure they end with a ? or I am likely not to realize that they are questions. :) ) -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/9321#comment:23 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12727 [Tor Browser]: Vanilla Tor Connectivity Issues In Iran -- Directory Authorities Blocked?
#12727: Vanilla Tor Connectivity Issues In Iran -- Directory Authorities Blocked? -+- Reporter: cda | Owner: tbb-team Type: defect | Status: new Priority: normal | Milestone: Component: Tor Browser |Version: Tor: 0.2.4.13-alpha Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+- Changes (by mrphs): * cc: mrphs (added) -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12727#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #3711 [Torsocks]: Application support for optimistic data: Torsocks
#3711: Application support for optimistic data: Torsocks --+--- Reporter: nickm | Owner: sysrqb Type: task | Status: needs_revision Priority: normal| Milestone: Component: Torsocks |Version: Resolution:| Keywords: performance roundtrip Actual Points:| Parent ID: Points:| --+--- Changes (by arma): * status: needs_review = needs_revision Comment: Setting to needs-revision to encourage David to show the world his dev branch. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/3711#comment:14 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #2874 [Firefox Patch Issues]: Block access to Components.interfaces from content script
#2874: Block access to Components.interfaces from content script -+- Reporter: mikeperry| Owner: mikeperry Type: enhancement | Status: needs_review Priority: normal | Milestone: Component: Firefox Patch|Version: Issues | Keywords: Resolution: | MikePerryIterationFires20110529, Actual Points: 1| backport-to-mozilla, Points: 4| MikePerry201408R | Parent ID: -+- Changes (by arthuredelstein): * keywords: MikePerryIterationFires20110529, backport-to-mozilla = MikePerryIterationFires20110529, backport-to-mozilla, MikePerry201408R * status: reopened = needs_review Comment: Components.interfaces has a different set of properties in ESR31 and ESR24. So I've reconsidered, and I think it's cleaner if we remove the Components.interfaces object from both ESR24 and ESR31 branches. That way, Components.interfaces won't be a method for content scripts to distinguish different versions of TorBrowser. I'm attaching a patch here that removes Components.interfaces for ESR24, and I'll be providing a similar patch to ESR31 for #12620. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/2874#comment:16 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12620 [Tor Browser]: Rebase TBB patches to Firefox 31 and add unit tests
#12620: Rebase TBB patches to Firefox 31 and add unit tests -+- Reporter: gk | Owner: tbb-team Type: task | Status: new Priority: major| Milestone: Component: Tor |Version: Browser| Keywords: TorBrowserTeam201408D, ff31-esr, Resolution: | tbb-rebase, tbb-firefox-patch Actual Points: | Parent ID: Points: | -+- Comment (by arthuredelstein): I've changed my mind -- I think we should remove Components.interfaces (for #2874) in ESR31 after all. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12620#comment:12 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12858 [Tor Browser]: routine bug report
#12858: routine bug report -+-- Reporter: newcombat| Owner: tbb-team Type: defect | Status: new Priority: normal | Milestone: Component: Tor Browser |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+-- Comment (by arma): What version of Tor, what bundle, etc? -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12858#comment:1 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12859 [Stem]: Improve parsing speed with profile-directed code tuning
#12859: Improve parsing speed with profile-directed code tuning -+ Reporter: nickm| Owner: atagar Type: enhancement | Status: new Priority: normal | Milestone: Component: Stem |Version: Keywords: | Actual Points: Parent ID: | Points: -+ Hi! I took a quick look at how Stem parses descriptors, and tried running cProfile over a networkstatus parse. I don't think I have all of the issues solved, but I managed to get a few of the hot spots calmed down for a speed reduction of about 30%. I don't promise that these are all correct, though I am pretty sure that the first one is a big win that you should take. It accounts for most of the speedup that I'm seeing. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12859 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12859 [Stem]: Improve parsing speed with profile-directed code tuning
#12859: Improve parsing speed with profile-directed code tuning
-+
Reporter: nickm| Owner: atagar
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Stem |Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-+
Comment (by nickm):
Actually, you could tighten up the new regex in 0002 even more. In my
profiles, it's faster still to use:
{{{
match_re = re.compile(r'^(%s)(?:[ \t]|$)' % |.join(keywords))
}}}
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/12859#comment:1
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12859 [Stem]: Improve parsing speed with profile-directed code tuning
#12859: Improve parsing speed with profile-directed code tuning -+-- Reporter: nickm| Owner: atagar Type: enhancement | Status: needs_review Priority: normal | Milestone: Component: Stem |Version: Resolution: | Keywords: Actual Points: | Parent ID: Points: | -+-- Changes (by nickm): * status: new = needs_review -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12859#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12848 [Tor]: Tor wrongly process circuit as connected to n_chan if create cell delivery failed
#12848: Tor wrongly process circuit as connected to n_chan if create cell delivery failed -+- Reporter: | Owner: cypherpunks| Status: needs_review Type: defect | Milestone: Tor: 0.2.4.x-final Priority: normal |Version: Tor: 0.2.5.5-alpha Component: Tor | Keywords: tor-relay 024-backport 023-backport Resolution: | Parent ID: Actual Points: | Points: | -+- Changes (by nickm): * milestone: Tor: 0.2.5.x-final = Tor: 0.2.4.x-final Comment: Merged into 0.2.5 and master. Possible backport if it doesn't cause any trouble. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12848#comment:15 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #3758 [Tor bundles/installation]: Remove out-of-date specifications from Tor 'Expert Bundle' for Windows (was: Tor 'Expert Bundle' for Windows contains out-of-date specifications)
#3758: Remove out-of-date specifications from Tor 'Expert Bundle' for Windows --+-- Reporter: rransom | Owner: erinn Type: defect| Status: new Priority: minor | Milestone: Component: Tor bundles/installation |Version: Resolution:| Keywords: needs-triage Actual Points:| Parent ID: Points:| --+-- -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/3758#comment:5 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #7970 [Tor bundles/installation]: Remove attic'ed bridges-spec.txt from NSIS installer
#7970: Remove attic'ed bridges-spec.txt from NSIS installer -+- Reporter: cypherpunks | Owner: erinn Type: defect | Status: new Priority: minor| Milestone: Component: Tor |Version: bundles/installation | Keywords: package_nsis-mingw.sh, Resolution: | tor-mingw.nsi.in, Windows, Actual Points: | installer, NSIS, bridges-spec.txt, Points: | attic, needs-triage | Parent ID: -+- Comment (by arma): I suggest closing this one as a duplicate of #3758, and then doing #3758. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/7970#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12860 [Tor]: Couldn't format create cell warning can be triggered remotely for relayed cells
#12860: Couldn't format create cell warning can be triggered remotely for
relayed
cells
-+-
Reporter: cypherpunks | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor |Version:
Keywords: tor-relay| Actual Points:
Parent ID: | Points:
-+-
If relay process extent request then it can to fill logs by warnings about
wrongly formatted create cells. It's easy to reproduce such cells and to
trigger logs for relay.
{{{
if (r 0) {
log_warn(LD_CIRC,Couldn't format create cell);
return -1;
}
}}}
It need lower logs level or rate limiting or LOG_PROTOCOL_WARN
(preferable) for relayed cells.
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/12860
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12815 [Orbot]: Changes is build not reflected in BUILD docs
#12815: Changes is build not reflected in BUILD docs -+ Reporter: o'darn | Owner: o'darn Type: task | Status: closed Priority: trivial | Milestone: Component: Orbot|Version: Resolution: fixed| Keywords: Actual Points: | Parent ID: Points: | -+ Changes (by o'darn): * status: accepted = closed * resolution: = fixed Comment: Pull request is at https://github.com/n8fr8/orbot/pull/4 -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12815#comment:6 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12860 [Tor]: Couldn't format create cell warning can be triggered remotely for relayed cells
#12860: Couldn't format create cell warning can be triggered remotely for
relayed
cells
-+---
Reporter: cypherpunks | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor |Version:
Resolution: | Keywords: tor-relay
Actual Points: | Parent ID:
Points: |
-+---
Comment (by cypherpunks):
Unless it checked before by circuit_extend()
{{{
if (extend_cell_parse(ec, rh.command,
cell-payload+RELAY_HEADER_SIZE,
rh.length) 0) {
log_fn(LOG_PROTOCOL_WARN, LD_PROTOCOL,
Can't parse extend cell. Closing circuit.);
return -1;
}
}}}
Then bug is invalid.
--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/12860#comment:1
Tor Bug Tracker Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
Re: [tor-bugs] #12860 [Tor]: Couldn't format create cell warning can be triggered remotely for relayed cells
#12860: Couldn't format create cell warning can be triggered remotely for relayed cells -+--- Reporter: cypherpunks | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Tor |Version: Resolution: invalid | Keywords: tor-relay Actual Points: | Parent ID: Points: | -+--- Changes (by cypherpunks): * status: new = closed * resolution: = invalid Comment: Seems so. Sorry. check_create_cell() called by extend_cell_parse() which is generates create cell. -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12860#comment:2 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
[tor-bugs] #12861 [- Select a component]: www.stamfordadvocate.com
#12861: www.stamfordadvocate.com +-- Reporter: wschloss@… | Owner: Type: defect | Status: new Priority: major | Milestone: Component: - Select a |Version: HTTPS-E chrome 2013.8.17 component | Actual Points: Keywords: remove rule | Points: Parent ID: | +-- This site does not work with your product. Please provide a way to remove this rule in Chrome version Jul 13,2014. Thank you. Not sure if I have the oorrect info below bacause i don't see about https Everywhere, anywhere. :) -- Ticket URL: https://trac.torproject.org/projects/tor/ticket/12861 Tor Bug Tracker Wiki https://trac.torproject.org/ The Tor Project: anonymity online ___ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
