From: swedebugia@riseup.net
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: torsocks 2.0 bug
Date: Fri, 29 Jan 2016 16:28:54 +0100 [thread overview]
Message-ID: <8b802d8294362c03c133c28a7fb7e3c4@riseup.net> (raw)
In-Reply-To: <20160129132809.1fe0c52e@debian-netbook>
On 2016-01-29 12:28, Efraim Flashner wrote:
> On Fri, 29 Jan 2016 11:45:59 +0100
> swedebugia@riseup.net wrote:
>
>> Hi
>>
>> I found after reconfiguring my system lately that the update to
>> torsocks
>> 2.0 broke this:
>>
>> $ torsocks icecat
>>
>> Which I use all the time.
>>
>> I tested with the former 2-3 versions of Icecat in my store and they
>> all
>> fail silently. Passing debug options does not give a clue to whats
>> wrong.
>
> What type of things don't work? That update was about 2.5 months ago,
> did you
> do all the normal things like rebooting after reconfiguring?
>
>> I tested torsocks 2.0 with youtube-dl and lynx and both work.
>>
>> I would like to patch tor.scm to have the option of installing an
>> earlier version of torsocks but dont know hot to check out the old
>> version.
>>
>> cheers swedebugia
>>
>
> here's the patch that updated torsocks. (attached)
>
> to have your own, custom torsocks from the previous version, you could
> add a
> file torsocks.scm, and build it with `guix build -f torsocks.scm`
>
> #:use-module ...
>
> (define-public torsocks-custom <-- I'm not sure if this line is
> necessary here
> (package (inherit torsocks)
> (name "torsocks-custom")
> (version "1.2")
> (source (origin
> (method url-fetch)
> (uri (string-append
> "http://torsocks.googlecode.com/files/torsocks-"
> version ".tar.gz"))
> (sha256
> (base32
>
> "1m0is5q24sf7jjlkl0icfkdc0m53nbkg0q72s57p48yp4hv7v9dy"))))
> (arguments '())
> (native-inputs '(()))))
Thanks for the tips.
I looked into torsocks and it seems:
* they moved to https://gitweb.torproject.org/torsocks.git
* there is a version 2.1 (from 8 months ago) here:
https://gitweb.torproject.org/torsocks.git/commit/?id=a43a3656a5bb4391fb1654d5ff44a5257e1f165f
* 2.0 branch is a complete rewrite of 1.3 which was the last stable
1.x-version.
https://lists.torproject.org/pipermail/tor-dev/2013-August/005319.html
I propose: we update to 2.1 first and see if this fixes the problem with
only icecat.
cheers
sdb
next prev parent reply other threads:[~2016-01-29 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 10:45 torsocks 2.0 bug swedebugia
2016-01-29 11:28 ` Efraim Flashner
2016-01-29 15:28 ` swedebugia [this message]
2016-02-03 9:40 ` Ludovic Courtès
2016-02-03 18:08 ` swedebugia
2016-02-03 19:33 ` Andreas Enge
2016-06-28 9:12 ` ng0
2016-08-01 15:37 ` ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b802d8294362c03c133c28a7fb7e3c4@riseup.net \
--to=swedebugia@riseup.net \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).