Re: [tor-bugs] #21394 [Core Tor/Tor]: connection timeouts are affecting Tor Browser usability

2017-04-09 Thread Tor Bug Tracker & Wiki
#21394: connection timeouts are affecting Tor Browser usability
+--
 Reporter:  arthuredelstein |  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-performance, tbb-usability  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by teor):

 This happened to me with Tor Browser 6.5.1 after my machine was asleep for
 5 minutes. Then, after it went to sleep and woke again, everything worked
 fine.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #15353 [Core Tor/Chutney]: Some chutney tests fail when localhost is the only available IP

2017-04-09 Thread Tor Bug Tracker & Wiki
#15353: Some chutney tests fail when localhost is the only available IP
---+--
 Reporter:  teor   |  Owner:  nickm
 Type:  defect | Status:  reopened
 Priority:  Low|  Milestone:
Component:  Core Tor/Chutney   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-chutney-usability  |  Actual Points:
Parent ID:  #21903 | Points:  2
 Reviewer: |Sponsor:  SponsorS-can
---+--
Changes (by teor):

 * parent:   => #21903


Comment:

 I think #21903 will fix this.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #16971 [Core Tor/Tor]: Testing tor networks use external DNS for dns checks

2017-04-09 Thread Tor Bug Tracker & Wiki
#16971: Testing tor networks use external DNS for dns checks
--+
 Reporter:  teor  |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Low   |  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:  Tor:
  |  unspecified
 Severity:  Normal| Resolution:
 Keywords:  lorax, tor-03-unspecified-201612  |  Actual Points:
Parent ID:  #21903| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * severity:   => Normal
 * parent:   => #21903


Comment:

 I think #21903 will fix this.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21903 [Core Tor/Chutney]: Disable DNS in chutney by default, and add an option to enable it

2017-04-09 Thread Tor Bug Tracker & Wiki
#21903: Disable DNS in chutney by default, and add an option to enable it
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #19573| Points:  0.5
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * parent:   => #19573


Comment:

 #19573 will use this option.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19573 [Core Tor/Chutney]: Use fixedresolver.py from dnslib in chutney

2017-04-09 Thread Tor Bug Tracker & Wiki
#19573: Use fixedresolver.py from dnslib in chutney
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * severity:  Normal => Minor


Comment:

 #21903 should make it easier to implement this.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20142 [Core Tor/Chutney]: chutney IPv6 HiddenServicePort tests

2017-04-09 Thread Tor Bug Tracker & Wiki
#20142: chutney IPv6 HiddenServicePort tests
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #17011| Points:  1
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 This should be easier now that we do IPv6 Exit checks.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20067 [Core Tor/Chutney]: Chutney should verify IPv6 SOCKSPorts (was: Chutney should verify IPv6 SOCKSPorts and IPv6 Exit traffic)

2017-04-09 Thread Tor Bug Tracker & Wiki
#20067: Chutney should verify IPv6 SOCKSPorts
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  testing, ipv6 |  Actual Points:
Parent ID:  #17011| Points:  1
 Reviewer:|Sponsor:
--+--

Old description:

> Chutney will soon verify using client to relay IPv6, but verify only
> sends traffic to and from tor over IPv4.
>
> We need to test the following:
> * IPv6 SOCKSPorts,
> * IPv4 and IPv6 SOCKSPorts with IPv6Traffic, and
> * IPv6 Exits
> * Hidden Services connecting to CHUTNEY_LISTEN_ADDRESS_V6:LISTEN_PORT

New description:

 Chutney will soon verify using client to relay IPv6, but verify only sends
 traffic to and from tor over IPv4.

 We need to test the following:
 * IPv6 SOCKSPorts,
 * IPv4 and IPv6 SOCKSPorts with IPv6Traffic, and
 * ~~IPv6 Exits~~
 * Hidden Services connecting to CHUTNEY_LISTEN_ADDRESS_V6:LISTEN_PORT

--

Comment (by teor):

 The exit part of this has been implemented: chutney has performed
 IPv6-only exit tests for a while now.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21632 [Core Tor/Chutney]: "Couldn't set up any working nameservers. Network not up yet? Will try again soon."

2017-04-09 Thread Tor Bug Tracker & Wiki
#21632: "Couldn't set up any working nameservers. Network not up yet?  Will try
again soon."
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #21903| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * parent:   => #21903


Comment:

 I think #21903 will fix this.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21903 [Core Tor/Chutney]: Disable DNS in chutney by default, and add an option to enable it

2017-04-09 Thread Tor Bug Tracker & Wiki
#21903: Disable DNS in chutney by default, and add an option to enable it
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:  0.5   |   Reviewer:
  Sponsor:|
--+--
 Due to #21900, we need to explicitly specify `ServerDNSResolvConfFile
 /dev/null` for chutney to work on macOS when the network is unavailable.

 We should also set `ServerDNSDetectHijacking 0`.

 This should be the default, because:
 * users who run chutney might not want it using DNS in a detectable
 pattern, and
 * it makes chutney more reliable, because it no longer depends on a
 working DNS.

 Some users will want chutney to be able to use hostnames, so we should add
 a tools/test-network.sh option and environmental variable to re-enable the
 default ServerDNSResolvConfFile setting (or, even better, use a custom
 ServerDNSResolvConfFile).

 There seems to be no reason to turn on ServerDNSDetectHijacking: some
 users might be using chutney with internal DNS names.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21902 [Core Tor/Tor]: evdns adds default DNS servers, but chutney wants a consistent environment

2017-04-09 Thread Tor Bug Tracker & Wiki
#21902: evdns adds default DNS servers, but chutney wants a consistent 
environment
--+-
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  chutney-wants, ipv6
Actual Points:|  Parent ID:
   Points:  1 |   Reviewer:
  Sponsor:|
--+-
 When we test tor exits using chutney, we want a consistent network
 environment, so that tests pass or fail reliably.

 This means that we want to be able to configure exits with no DNS servers,
 and have them only connect to IP addresses.

 But evdns adds default name server(s) in some circumstances (for example,
 127.0.0.1:53.)

 This default could also be an issue on an IPv6-only system, where we'd
 want [::1]:53. (Yes, some IPv6-only systems don't even have an IPv4
 localhost!)

 This is also broken because of the empty/missing resolv.conf behaviour in
 #21900.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21281 [Core Tor/Tor]: Allow process poll rate to be customized

2017-04-09 Thread Tor Bug Tracker & Wiki
#21281: Allow process poll rate to be customized
---+--
 Reporter:  atagar |  Owner:
 Type:  enhancement| Status:  new
 Priority:  Very Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor   |Version:
 Severity:  Trivial| Resolution:
 Keywords:  stem-wants, chutney-wants  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by teor):

 * keywords:   => stem-wants, chutney-wants


Comment:

 Chutney would also benefit from this after #20409 is implemented using
 OwningControllerProcess.

 (I think we'll need to set it to 1 second to avoid a failure in one `make
 test-network-all` test affecting subsequent tests.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21901 [Core Tor/Chutney]: Make tor clean up before terminating a chutney network

2017-04-09 Thread Tor Bug Tracker & Wiki
#21901: Make tor clean up before terminating a chutney network
--+-
 Reporter:  teor  |  Owner:  teor
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal|   Keywords:  coverage, stats
Actual Points:  0.5   |  Parent ID:
   Points:  0.5   |   Reviewer:
  Sponsor:|
--+-
 This increases integration test coverage, and improves the reliability of
 any statistics being gathered.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21900 [Core Tor/Tor]: evdns fails when resolv.conf is missing, but succeeds when resolv.conf is empty

2017-04-09 Thread Tor Bug Tracker & Wiki
#21900: evdns fails when resolv.conf is missing, but succeeds when resolv.conf 
is
empty
--+-
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  technical-debt, dns
Actual Points:|  Parent ID:
   Points:  2 |   Reviewer:
  Sponsor:|
--+-
 When tor's ServerDNSResolvConfFile (default /etc/resolv.conf) is missing,
 evdns does not add any name servers, and therefore Exits do not allow any
 exit traffic (not even IP-based traffic):
 {{{
 [debug] configure_nameservers: stat()ing /etc/resolv.conf
 [warn] Unable to stat resolver configuration in '/etc/resolv.conf': No
 such file or directory
 [info] mark_my_descriptor_dirty: Decided to publish new relay descriptor:
 dns resolvers failed
 }}}

 This happens on macOS when the network is down. On macOS, /etc/resolv.conf
 is symlinked to /var/run/resolv.conf. When the network is down, macOS
 deletes /var/run/resolv.conf, so the stat() call on /etc/resolv.conf
 fails.

 But when tor's ServerDNSResolvConfFile is empty, evdns adds a default name
 server (127.0.0.1:53 on my macOS), and therefore Exits allow exit traffic:
 {{{
 [info] eventdns: Parsing resolv.conf file /dev/null
 [info] eventdns: Added nameserver 127.0.0.1:53 as 0x61509e00
 [info] mark_my_descriptor_dirty: Decided to publish new relay descriptor:
 dns resolvers failed
 [info] eventdns: Parsing resolv.conf file /dev/null
 ...
 [info] mark_my_descriptor_dirty: Decided to publish new relay descriptor:
 dns resolvers back
 }}}

 We should also stop the extra descriptor upload:
 {{{
 [info] mark_my_descriptor_dirty: Decided to publish new relay descriptor:
 dns resolvers failed
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21796 [Core Tor/Tor]: missing evutil_secure_rng_add_bytes()

2017-04-09 Thread Tor Bug Tracker & Wiki
#21796: missing evutil_secure_rng_add_bytes()
---+---
 Reporter:  cypherpunks|  Owner:
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  030-backport 029-backport  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by cypherpunks):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 fixed in libevent commit 266f43af7798befa3d27bfabaa9ae699259c3924

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21899 [- Select a component]: Address setting ignoring IPv6

2017-04-09 Thread Tor Bug Tracker & Wiki
#21899: Address setting ignoring IPv6
--+
 Reporter:  ItsNannerpuss |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.7.x-final
Component:  - Select a component  |Version:  Tor: 0.2.7.6
 Severity:  Normal| Resolution:
 Keywords:  ipv6  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 Tor relays require IPv4 addresses for the foreseeable future.
 You can not setup a tor relay without IPv4.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21899 [- Select a component]: Address setting ignoring IPv6

2017-04-09 Thread Tor Bug Tracker & Wiki
#21899: Address setting ignoring IPv6
--+
 Reporter:  ItsNannerpuss |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.7.x-final
Component:  - Select a component  |Version:  Tor: 0.2.7.6
 Severity:  Normal|   Keywords:  ipv6
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 According to the torrc man page:

 "Address: The IP address or fully qualified domain name of this server
 (e.g. moria.mit.edu)."

 In torrc, set the Address to an IPv6 address and port using standard
 notation:

 Address [1234:5678::01:1234]

 

 The tor server starts up, and doesn't appear to give any relevant
 warnings, but log output suggests tor is ignoring the address setting and
 guessing anyway.

 Apr 09 15:50:52.000 [notice] Guessed our IP address as 1.2.3.4 (source:
 5.6.7.8).

 This server is configured only with IPv6 settings for tor, and the goal is
 to have it ignore any IPv4 addresses present on the host, so this behavior
 is undesirable.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21710 [Applications/Tor Browser]: Upgrade Go to 1.8.1 (was: Upgrade Go to 1.8)

2017-04-09 Thread Tor Bug Tracker & Wiki
#21710: Upgrade Go to 1.8.1
--+--
 Reporter:  dcf   |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Description changed by dcf:

Old description:

> * [https://blog.golang.org/go1.8 blog post]
>  * [https://golang.org/doc/go1.8 release notes]
>
> Note:
> > Go 1.8 now only supports OS X 10.8 or later. This is likely the last Go
> release to support 10.8. Compiling Go or running binaries on older OS X
> versions is untested.
>
> See also #21709 for Go 1.7.5. I'm going to test a 1.7.5 patch before
> working on 1.8.

New description:

 * [https://blog.golang.org/go1.8 blog post]
  * [https://golang.org/doc/go1.8 release notes]
  * [https://golang.org/doc/devel/release.html#go1.8.minor minor release
 notes]

 Note:
 > Go 1.8 now only supports OS X 10.8 or later. This is likely the last Go
 release to support 10.8. Compiling Go or running binaries on older OS X
 versions is untested.

 See also #21709 for Go 1.7.5. I'm going to test a 1.7.5 patch before
 working on 1.8.

--

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21816 [Core Tor/Tor]: Add support for Pluggable Transports 2.0

2017-04-09 Thread Tor Bug Tracker & Wiki
#21816: Add support for Pluggable Transports 2.0
--+--
 Reporter:  chelseakomlo  |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * cc: dcf (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18002 [Archived/operations]: move away from OFTC to new functional, Tor-friendly IRC network

2017-04-09 Thread Tor Bug Tracker & Wiki
#18002: move away from OFTC to new functional, Tor-friendly IRC network
-+---
 Reporter:  adrelanos|  Owner:
 Type:  task | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Archived/operations  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  None
-+---

Comment (by cypherpunks):

 UMODE_INVISIBLE yet

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18002 [Archived/operations]: move away from OFTC to new functional, Tor-friendly IRC network

2017-04-09 Thread Tor Bug Tracker & Wiki
#18002: move away from OFTC to new functional, Tor-friendly IRC network
-+---
 Reporter:  adrelanos|  Owner:
 Type:  task | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Archived/operations  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  None
-+---

Comment (by cypherpunks):

 oftc and PRIVACY:
 {{{
 if (((i = can_join(source_p, chptr, key)) && !IsGod(source_p)))
 {
   sendto_one(source_p, form_str(i), me.name,
  source_p->name, chptr->chname);
   if(i == ERR_TOOMANYCHANNELS)
   break;
   else
   continue;
 }

 if(i != 0 && IsGod(source_p) && MyClient(source_p))
 {
   char tmp[IRCD_BUFSIZE];
   ircsprintf(tmp, "%s is using God mode: JOIN %s", source_p->name,
   chptr->chname);
   sendto_gnotice_flags(UMODE_SERVNOTICE, L_ALL, me.name, , NULL,
   tmp);
   oftc_log(tmp);
 }
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18002 [Archived/operations]: move away from OFTC to new functional, Tor-friendly IRC network

2017-04-09 Thread Tor Bug Tracker & Wiki
#18002: move away from OFTC to new functional, Tor-friendly IRC network
-+---
 Reporter:  adrelanos|  Owner:
 Type:  task | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Archived/operations  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  None
-+---

Comment (by cypherpunks):

 dwfreed said. oftc's  ir.cop:
 > IRC is not a democracy, especially not OFTC
 > I don't care what you think

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21897 [Internal Services/Service - lists]: Please create a global-south mailing list

2017-04-09 Thread Tor Bug Tracker & Wiki
#21897: Please create a global-south mailing list
---+
 Reporter:  sukhbir|  Owner:  qbi
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by qbi):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I created the list, added sukhbir as maintainer and also added the list to
 https://trac.torproject.org/projects/tor/wiki/doc/emailLists

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17956 [Core Tor/Tor]: Let tor handle disconnects better

2017-04-09 Thread Tor Bug Tracker & Wiki
#17956: Let tor handle disconnects better
+--
 Reporter:  dns2utf8|  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:  Tor:
|  0.2.7.5
 Severity:  Normal  | Resolution:
 Keywords:  network, tor-03-unspecified-201612  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by tokotoko):

 * cc: fdsfgs@… (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #15765 [Core Tor/Tor]: Tor doesn't reconnect automatically when tun/tap device goes down.

2017-04-09 Thread Tor Bug Tracker & Wiki
#15765: Tor doesn't reconnect automatically when tun/tap device goes down.
---+--
 Reporter:  cypherpunks|  Owner:
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor   |Version:  Tor: unspecified
 Severity:  Normal | Resolution:
 Keywords:  tor-03-unspecified-201612  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by tokotoko):

 * cc: fdsfgs@… (added)
 * severity:   => Normal


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21896 [Applications/Tor Browser]: CAPTCHA challenge not displaying on a news website when trying to post a comment

2017-04-09 Thread Tor Bug Tracker & Wiki
#21896: CAPTCHA challenge not displaying on a news website when trying to post a
comment
--+--
 Reporter:  laurus|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by laurus):

 * severity:  Normal => Major


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #16010 [Applications/Tor Browser]: Get a working content process sandbox for Tor Browser on Windows

2017-04-09 Thread Tor Bug Tracker & Wiki
#16010: Get a working content process sandbox for Tor Browser on Windows
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-gitian, tbb-security,  |  Actual Points:
  TorBrowserTeam201704, tbb-7.0-must-alpha,  |
  GeorgKoppen201704  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by cypherpunks):

 Detailed description of why SEH4 and SEHOP were created
 http://www.uninformed.org/?v=5=2=txt

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs