[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #33560 [- Select a component]: Settings immediately after install

To: undisclosed-recipients: ;
Subject: [tor-bugs] #33560 [- Select a component]: Settings immediately after install
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Mon, 09 Mar 2020 05:06:27 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 09 Mar 2020 01:06:38 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
Reply-to: no-reply@xxxxxxxxxxxxxx, blackhole@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#33560: Settings immediately after install
-------------------------------+--------------------------------------
 Reporter:  KatBloodgood       |          Owner:  (none)
     Type:  defect             |         Status:  new
 Priority:  Medium             |      Component:  - Select a component
  Version:  Tor: unspecified   |       Severity:  Normal
 Keywords:  client-transport?  |  Actual Points:
Parent ID:                     |         Points:
 Reviewer:                     |        Sponsor:
-------------------------------+--------------------------------------
 3/9/20, 04:33:18.780 [NOTICE] Bootstrapped 10% (conn_done): Connected to a
 relay
 3/9/20, 04:33:19.122 [NOTICE] Bootstrapped 14% (handshake): Handshaking
 with a relay
 3/9/20, 04:33:19.336 [NOTICE] Bootstrapped 15% (handshake_done): Handshake
 with a relay done
 3/9/20, 04:33:19.337 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded
 enough directory info to build circuits
 3/9/20, 04:33:19.338 [NOTICE] Bootstrapped 90% (ap_handshake_done):
 Handshake finished with a relay to build circuits
 3/9/20, 04:33:19.340 [NOTICE] Bootstrapped 95% (circuit_create):
 Establishing a Tor circuit
 3/9/20, 04:33:20.168 [NOTICE] Bootstrapped 100% (done): Done
 3/9/20, 04:33:21.105 [NOTICE] New control connection opened from
 127.0.0.1.
 3/9/20, 04:33:21.354 [NOTICE] New control connection opened from
 127.0.0.1.
 3/9/20, 04:34:59.416 [WARN] CreateProcessA() failed: The system cannot
 find the file specified.
 3/9/20, 04:34:59.416 [WARN] Pluggable Transport process terminated with
 status code 0
 3/9/20, 04:34:59.417 [WARN] Failed to start process: (null)
 3/9/20, 04:34:59.417 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
 3/9/20, 04:34:59.417 [NOTICE] Switching to guard context "bridges" (was
 using "default")
 3/9/20, 04:34:59.504 [NOTICE] Delaying directory fetches: No running
 bridges
 3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:00.507 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:00.508 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:00.509 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:01.511 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:01.511 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:02.523 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:02.523 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:03.529 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:03.529 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:04.542 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:04.543 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:05.546 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:06.556 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:06.556 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:07.582 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:07.583 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:07.584 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:08.567 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:09.575 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:09.576 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:11.593 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:12.611 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:14.621 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:15.635 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:16.645 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:17.648 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:18.660 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:19.672 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:22.546 [WARN] CreateProcessA() failed: The system cannot
 find the file specified.
 3/9/20, 04:35:22.547 [WARN] Pluggable Transport process terminated with
 status code 0
 3/9/20, 04:35:22.547 [WARN] Failed to start process: (null)
 3/9/20, 04:35:22.548 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
 3/9/20, 04:35:22.760 [NOTICE] Bridge at '217.12.199.130:42367' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:22.760 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable
 by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:22.760 [NOTICE] Bridge at '96.41.145.139:42260' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:23.767 [NOTICE] Bridge at '217.12.199.130:42367' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:23.767 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable
 by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:23.767 [NOTICE] Bridge at '96.41.145.139:42260' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:24.759 [NOTICE] Bridge at '217.12.199.130:42367' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:24.759 [NOTICE] Bridge at '96.41.145.139:42260' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:25.759 [NOTICE] Bridge at '217.12.199.130:42367' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:25.759 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable
 by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:26.771 [NOTICE] Bridge at '217.12.199.130:42367' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:26.771 [NOTICE] Bridge at '96.41.145.139:42260' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:27.790 [NOTICE] Bridge at '217.12.199.130:42367' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:27.791 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable
 by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:28.775 [NOTICE] Bridge at '217.12.199.130:42367' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:28.775 [NOTICE] Bridge at '96.41.145.139:42260' isn't
 reachable by our firewall policy. Asking bridge authority instead.
 3/9/20, 04:35:29.290 [WARN] CreateProcessA() failed: The system cannot
 find the file specified.
 3/9/20, 04:35:29.290 [WARN] Pluggable Transport process terminated with
 status code 0
 3/9/20, 04:35:29.290 [WARN] Failed to start process: (null)
 3/9/20, 04:35:29.300 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
 3/9/20, 04:35:29.761 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:29.761 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:29.761 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:30.763 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:30.763 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:30.763 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33560>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Follow-Ups:
- Re: [tor-bugs] #33560 [Circumvention/Obfs4]: Settings immediately after install
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33560 [Circumvention/Obfs4]: Settings immediately after install
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33560 [- Select a component]: Settings immediately after install
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #33560 [Circumvention/Obfs4]: Settings immediately after install
  - From: Tor Bug Tracker & Wiki

Prev by Author: Re: [tor-bugs] #33638 [Circumvention/Snowflake]: Refactor (De)SerializeSessionDescription as common utils
Next by Author: Re: [tor-bugs] #33693 [Circumvention/Snowflake]: snowflake's 0.0.3.0 dummy address means rate limits are skipped means BW controller events show no bandwidth used
Previous by thread: [tor-bugs] #33559 [Applications/Tor Browser]: Update tor-android-service To Use Updated Android Toolchain
Next by thread: Re: [tor-bugs] #33560 [- Select a component]: Settings immediately after install
Index(es):
- Author
- Thread