Re: [tor-talk] obfsproxy failure: obfs3

[lee colleton <lee@xxxxxxxxxxxx>]

There's a more serious issue in that my server doesn't appear to be
reachable. I've opened tcp:443,9001 along with the two specifiedobfsproxy
ports

Aug 14 15:26:58.000 [notice] Bootstrapped 100%: Done.
Aug 14 15:26:58.000 [notice] Now checking whether ORPort
173.255.119.202:443 is reachable... (this may take up to 20 minutes --
look for log messages indicating success)
Aug 14 15:28:00.000 [notice] New control connection opened.
Aug 14 15:46:56.000 [warn] Your server (173.255.119.202:443) has not
managed to confirm that its ORPort is reachable. Please check your
firewalls, ports, address, /etc/hosts file, etc.



On Wed, Aug 14, 2013 at 8:46 AM, lee colleton <lee@xxxxxxxxxxxx> wrote:

> The packaged version of tor complains about support for faster OpenSSL:
>
> Aug 14 15:26:52.000 [notice] Tor 0.2.4.16-rc (git-dcf6b6d7dda9ffbd) opening log file.
> Aug 14 15:26:52.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.
>
>
>
> On Wed, Aug 14, 2013 at 8:41 AM, lee colleton <lee@xxxxxxxxxxxx> wrote:
>
>> My intent is to set up an obfsproxy bridge in the manner of the EC2
>> images available from cloud.torproject.org which will stay up to date
>> thanks to unattended upgrades. I've enabled wheezy-backports and upgraded
>> thus:
>>
>> lee@tor-bootstrap:~$ dpkg -l tor obfsproxy
>> Desired=Unknown/Install/Remove/Purge/Hold
>> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>> ||/ Name                            Version              Architecture         Description
>> +++-===============================-====================-====================-====================================================================
>> ii  obfsproxy                       0.2.1-2~wheezy+1     all                  pluggable transport proxy for Tor
>> ii  tor                             0.2.4.16-rc-1~d70.wh amd64                anonymizing overlay network for TCP
>> lee@tor-bootstrap:~$ apt-cache showpkg tor
>> Package: tor
>> Versions:
>> 0.2.4.16-rc-1~d70.wheezy+1 (/var/lib/apt/lists/deb.torproject.org_torproject.org_dists_experimental-wheezy_main_binary-amd64_Packages) (/var/lib/dpkg/status)
>>
>>
>>
>> On Wed, Aug 14, 2013 at 2:53 AM, George Kadianakis <desnacked@xxxxxxxxxx>wrote:
>>
>>> Hi lee,
>>>
>>> it seems like you are using an old version of obfsproxy which does not
>>> support obfs3. obfsproxy was recently rewritten in Python and that's
>>> the version you want to use (the version you are currently using is
>>> written in C). That is, you are currently using obfsproxy-0.1.4 but
>>> you should be using obfsproxy-0.2.1.
>>>
>>> As seen in http://packages.debian.org/obfsproxy you can find
>>> obfsproxy-0.2.1-3 through wheezy-backports. Or you can install it
>>> manually using
>>> https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en
>>> .
>>>
>>> --
>>> tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
>>> To unsusbscribe or change other settings go to
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>>>
>>
>>
>
-- 
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk