On 8/26/13, David Goulet wrote:
> Can you retry with the new upstream master? Some patches went in for BSD
> support
Tried this earlier and it compiled clean. Haven't tested it.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproj
Thanks David,
I've got the upstream changes which fixes quite a few things, so thank
you.
I've made some minor changes to make gcc happy which I've sent through
in a pull request [1] and perhaps you can offer some feedback to
ensure best practices are followed if needed.
Apart from that it's bui
Hi Luke,
Can you retry with the new upstream master? Some patches went in for BSD support
fixing the SO_DOMAIN issue.
Thanks!
David
Luke Gallagher:
> Hi David,
>
> Thanks for your effort on the new version of Torsocks.
>
> I've had a brief look at getting a working build on OSX (10.8.4),
> how
Hi,
K. Raven:
> Hi,
>
>> I'm asking the community for feedbacks, testing, code review,
>> optimization design and/or anything useful to help improve the
>> project (even correcting the mistakes or improving any comments).
>
> under Kubuntu 13.04:
>
> $ make
> Making all in src
> make[1]: Betret
Hi,
> I'm asking the community for feedbacks, testing, code review,
> optimization design and/or anything useful to help improve the
> project (even correcting the mistakes or improving any comments).
under Kubuntu 13.04:
$ make
Making all in src
make[1]: Betrete Verzeichnis '/opt/git/torsocks/s
Hi David,
Thanks for your effort on the new version of Torsocks.
I've had a brief look at getting a working build on OSX (10.8.4),
however I've run into a few problems, which I'm attempting to work
through, but I'm not entirely sure how to fix all of them, I'll see how
far I get.
The syscalls ar
Greetings everyone!
Two months ago I sent an email [1] to the tor-dev mailing list explaining some
important issues with torsocks. I proposed myself to do a complete rewrite for
the reasons detailed in the email.
I've released today the first release candidate for a 2.0.0 version.
https://github
