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

Re: [tor-bugs] #20250 [Obfuscation/meek]: macOS 10.12 TorBrowser meek pluggable transport issues

#20250: macOS 10.12 TorBrowser meek pluggable transport issues
-------------------------------------------------+-------------------------
 Reporter:  tordevSZ0                            |          Owner:  dcf
     Type:  defect                               |         Status:  new
 Priority:  High                                 |      Milestone:
Component:  Obfuscation/meek                     |        Version:  Tor:
                                                 |  unspecified
 Severity:  Major                                |     Resolution:
 Keywords:  meek, macOS, TorBrowser, 10.12,      |  Actual Points:
  sierra, macOS                                  |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by tordevSZ0):

 Replying to [comment:6 cypherpunks]:
 > > On the same machine running 10.11.6 before upgrade, TorBrowser with
 both of the meek transports worked fine.
 >
 > It's probably coincidence. Might be censors update their filters too?
 >
 > > By modifying the meek PT in torrc-defaults the connection fails
 immediately.
 >
 > Can you test your configuration outside of censored network? Or test it
 with modified front for
 [https://trac.torproject.org/projects/tor/wiki/doc/meek meek]

 I really don't think it is a coincidence. As I said here
 https://trac.torproject.org/projects/tor/ticket/20251#comment:5, I am
 acecssing TRAC using meek with TorBrowser on 10.11.6 right now without any
 problems while two machines running fresh installs of 10.12 in the same
 country as the 10.11.6 installation, with clean installs of TorBrowser are
 unable to maintain the meek connections.

 If you read through
 https://trac.torproject.org/projects/tor/ticket/20250?replyto=6#comment:5,
 especially at the end of the log, and the line:


 "650 WARN The connection to the SOCKS4 proxy server at 127.0.0.1:57343
 just failed. Make sure that the proxy server is up and running."

 in the main ticket, it seems meek-client is crashing.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20250#comment:7>
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