On 28 Feb (22:19:39), Roger Dingledine wrote:
> On Wed, Feb 26, 2014 at 02:06:25PM +0100, Jeroen Massar wrote:
> > On 2014-02-26 13:46, Jacob Appelbaum wrote:
> > > I think this is a fine idea - if no one objects, I'll purge it.
> >
> > No objection per-se, but a recommendation/check-up:
>
> Soun
On 13 Aug (15:47:43), George Kadianakis wrote:
> Hello friends :)
>
> This is a post to discuss how Tor should treat its entry guards when
> its network goes down. This is part of ticket #12595 [0] which aims to
> design better interfaces and data structures for entry guards.
>
> This thread inve
Hi everyone!
Following the discussion of bug #10007[1], this is the *stable* release 2.0.0
for torsocks. Nothing major went in since -rc7, see the change log below.
2014-08-11 torsocks 2.0.0
* Fix: compilation issue on Debian kfreebsd-i386
* Fix: add LICENSE file to repository
* Fix:
Hi everyone!
Took me a while to do it but there it is! For those not following
torsocks development, this is a status report of the project.
As of April 4th 2014, the release candidate 7 was released. With that
release, the main code is now on torproject.org which is now the
official upstream of
gt;
> On 2/23/14, Virgil Griffith wrote:
> > Sitting with David Goulet, it's problematic that when I search for
> > "torsocks" I get the old Google Code page instead of the up-to-date
> > page on http://gitweb.torproject.org
> >
> > This i
Hi everyone!
This is the release candidate 7 for torsocks 2.x. Nothing major, fixes
and some code refactoring went in.
From this point on, the upstream torsocks git[1] is now updated with
that new code in the master branch but no stable release yet. With that,
my github repository will become a m
Hi everyone!
Here is the release candidate 5 *and* 6 for Torsocks 2.x. Unfortunately,
right after the release 5, I've noticed a critical issue that made the
new allow inbound option misbehaved quite badly so I'm immediately
releasing rc6 containing that fix. Basically, you can ignore rc5 if you
pr
On 08 Mar (06:12:41), Yawning Angel wrote:
> On Fri, 7 Mar 2014 10:45:14 -0500
> David Goulet wrote:
>
> > Quoting rfc1928:
> >
> > "When a reply (REP value other than X'00') indicates a failure, the
> > SOCKS server MUST terminate the TCP conn
On 07 Mar (14:03:35), Yawning Angel wrote:
> Sorry this response took so long. I've been kind of busy.
>
> On Sat, 01 Mar 2014 13:57:34 +0100
> "Sebastian G. " wrote:
>
> > To me it is clear that the two are messed up, but I'm not sure what's
> > the correct order.
>
> Indeed. Since there isn
On 04 Mar (10:46:06), David Goulet wrote:
> On 04 Mar (10:30:40), Nick Mathewson wrote:
> > On Tue, Mar 4, 2014 at 10:13 AM, David Goulet wrote:
> > > On 04 Mar (08:36:13), Nick Mathewson wrote:
> > >> On Mar 4, 2014 4:26 AM, "Lunar" wrote:
> > >
On 04 Mar (10:30:40), Nick Mathewson wrote:
> On Tue, Mar 4, 2014 at 10:13 AM, David Goulet wrote:
> > On 04 Mar (08:36:13), Nick Mathewson wrote:
> >> On Mar 4, 2014 4:26 AM, "Lunar" wrote:
> >> >
> >> > David Goulet:
> >> > &
On 04 Mar (08:36:13), Nick Mathewson wrote:
> On Mar 4, 2014 4:26 AM, "Lunar" wrote:
> >
> > David Goulet:
> > > After a big code review from Nick and help from a lot of people
> > > contributing and testing, this is the release candidate 4 for the new
Hi everyone!
After a big code review from Nick and help from a lot of people
contributing and testing, this is the release candidate 4 for the new
torsocks.
Hopefully this is the last stretched before pushing this effort upstream
but for that we need help with code/documentation review (again) an
On 28 Feb (22:19:39), Roger Dingledine wrote:
> On Wed, Feb 26, 2014 at 02:06:25PM +0100, Jeroen Massar wrote:
> > On 2014-02-26 13:46, Jacob Appelbaum wrote:
> > > I think this is a fine idea - if no one objects, I'll purge it.
> >
> > No objection per-se, but a recommendation/check-up:
>
> Soun
On 24 Feb (10:54:59), Nick Mathewson wrote:
> Hi, all!
>
> We're going to start trying to have a developer's meeting for working
> on the program "tor". (This won't cover all the other programs
> developed under the Tor umbrella.)
>
> My tentative plan is to do it on the #tor-dev IRC channel, u
Greetings everyone!
After Fosdem 2014, I had the chance to talk with a lot of people about
Torsocks and the current status. It appears it's actually quite used!
(more than I thought). I've already received multiple contributions
after a quick announcement of the project during my talk.
This email
On 27 Jan (14:58:04), Luke Gallagher wrote:
> Hi David,
>
> Just wanted to give you a heads up to let you know that I'm back looking
> at the tests for torsocks, as its has been a while since the last few
> commits for tests (things got a little busy towards the end of last
> year). I'm continuing
On 30 Nov (19:56:11), Nick Mathewson wrote:
> On Tue, Nov 26, 2013 at 5:17 PM, David Goulet wrote:
> > Hi everyone,
> >
> > The torsocks 2.0-rc3 code is getting quite stable in my opinion. There
> > are still some issues but nothing feature critical.
> >
>
Hi again,
Sorry for the delay to respond!
On 10 Dec (20:27:14), t...@herr-der-mails.de wrote:
> Hello David,
>
> thank you for your reaction. I've read some information about
> "Torsocks" now and yes, it seems to be similar. Unfortunately the
> information on Torsocks's homepage is rather shor
Hi!
On 06 Dec (18:59:33), t...@herr-der-mails.de wrote:
> Hello,
>
> I've first sent this e-mail to h...@rt.torproject.org and the answer
> was to send a copy of it to the "tor-dev mailing list". So that's
> what I do:
>
> I just wanted to let you know that I've created a small new tool for
>
On 30 Nov (14:22:19), Philipp Winter wrote:
> On Fri, Nov 29, 2013 at 11:37:27AM -0500, David Goulet wrote:
> > On 29 Nov (15:07:41), Philipp Winter wrote:
> >> I also have a minor feature request. It would be great if
> >> torsocks could display the source IP address a
On 29 Nov (15:07:41), Philipp Winter wrote:
> On Tue, Nov 26, 2013 at 05:17:58PM -0500, David Goulet wrote:
> > I would really love to have help with code review so it can get accepted
> > as a replacement in the near future. Some of you already gave feedbacks
> > so thanks
Hi everyone,
The torsocks 2.0-rc3 code is getting quite stable in my opinion. There
are still some issues but nothing feature critical.
https://github.com/dgoulet/torsocks
I would really love to have help with code review so it can get accepted
as a replacement in the near future. Some o
On 05 Nov (14:25:25), David Goulet wrote:
> On 05 Nov (16:14:33), Thomas Klausner wrote:
> >
> > And what is the point of src.old inside the tarball?
>
> This is temporary, it contains the source of the previous version (1.3)
> and I keep them there as a reference for
On 05 Nov (16:14:33), Thomas Klausner wrote:
> Hi!
>
> I've patched torsocks-v2.0.0-rc3 to compile on NetBSD.
>
> There is one warning left:
> syscall.c: In function 'handle_mmap':
> syscall.c:88:9: warning: cast from pointer to integer of different size
I encountered that on FreeBSD but I can't
Hi everyone!
I just pushed the 2.0.0-rc3 tag for the torsocks rewrite.
https://github.com/dgoulet/torsocks/archive/v2.0.0-rc3.tar.gz
Important fixes got in especially with the testing done with firefox lately.
The good news is that it works well with firefox now :). Of course, you should
ALWAYS
Apparently, I failed to put the person in CC :).
On 02 Nov (13:47:56), David Goulet wrote:
> On 02 Nov (19:25:42), Maxim Kammerer wrote:
> > On Sat, Nov 2, 2013 at 5:58 PM, David Goulet wrote:
> > > For now, it would only be .i2p address support (like .onion). In
> > &
On 02 Nov (19:25:42), Maxim Kammerer wrote:
> On Sat, Nov 2, 2013 at 5:58 PM, David Goulet wrote:
> > For now, it would only be .i2p address support (like .onion). In
> > torsocks, it's not that difficult to support both addressing.
>
> Does I2P's SOCKS proxy work
On 02 Nov (16:13:37), adrelanos wrote:
> Hi David,
>
> adding .i2p support to torsocks is perfectly fine. It's a feature, not a
> limitation. Who doesn't want to use it won't be annoyed by it. (Other
> than man page and --help entry, but well, life is tough. :)
>
> Someone else already said on th
Greetings everyone!
I've been approached by I2P folks for adding ".i2p" address support in
Torsocks. Since what torsocks does can be applied for both Tor and I2P,
they felt that duplicating was not a good idea thus asking if merging
both systems make sense and is possible.
For now, it would only
On 30 Oct (23:07:18), Lunar wrote:
> David Goulet:
> > Ok, I manage to make it work with Firefox.
>
> Yeah! :)
>
> > However, and a BIG however, this is a special fix for specific case
> > where memory allocation is handle by the application AND syscall() is
&
On 30 Oct (12:28:19), Lunar wrote:
> Lunar:
> > David Goulet:
> > > Now the issue was detected with firefox which uses a custom malloc hook
> > > meaning that it handles its own memory allocation. This hook uses mmap()
> > > that firefox redefines to be
On 29 Oct (16:41:02), Ian Goldberg wrote:
> On Tue, Oct 29, 2013 at 03:10:50PM -0400, David Goulet wrote:
> > That would work if there is a way I can "differ" the hijack of the
> > syscall symbol... Unfortunately, this is done at linking time thus
> > during run time
On 29 Oct (14:58:44), Nick Mathewson wrote:
> On Tue, Oct 29, 2013 at 2:38 PM, David Goulet wrote:
>
> > To be honest, I am not sure what's the right fix here or if there is any
> > way to lookup the symbol in a "special" way that would help here. Any
>
Hi everyone,
I stumble upon an issue when testing torsocks[1] with firefox. I'm still
wondering how this can be fixed thus I need more eyes on this :). The
issue is that torsocks gets into a deadlock during the initialization
phase within the libc.
Here it is. This new torsocks version hijacks th
But, this is the more painful part because it's not that trivial to test if our
connection went through Tor or not. check.tpo is a good start for that I guess
:). There is some features also like inet socket passing through Unix socket
that torsocks is suppose to deny, some syscall() also,
Sure and please don't hesitate to ask any questions or any comments!
You can find me on IRC if you'll like to discuss things.
Cheers!
David
On 06 Sep (10:12:08), Luke Gallagher wrote:
> On 6/09/13 9:52 AM, David Goulet wrote:
> > So yes, please if you like to contribute mor
Hi Luke,
That would be awesome!
Currently, I've already added some basic DNS tests and also unit test
for some subsystem in common/.
It uses libtap and integrated with make check also right now.
So yes, please if you like to contribute more tests, that would be
great!
Cheers!
David
On 06 Sep
Greetings everyone!
After a week or so, the release candidate 2 is now out after receiving various
contributions for BSD and OS X support.
A quick note. Please use the Github bug tracker for any issues and *not*
trac.torproject.org. Until this code base is accepted as a potential replacement
for
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
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
am
> understanding the pure C code fairly well at this point. What's the next
> thing that needs to be done? I am free for the next couple of days, so I can
> work on whatever. I have Mint running in a VM, but OS X is my primary OS for
> development.
>
>
> On Jun
Matthew Finkel:
> On Thu, Jun 27, 2013 at 03:11:23PM -0400, David Goulet wrote:
>> Ian Goldberg:
>>> Are non-blocking sockets, select/poll/etc. (especially at connect()
>>> time), and optimistic data on the to-do list?
>>
>> Yes! Good point I should ha
Ian Goldberg:
> On Wed, Jun 26, 2013 at 03:55:58PM -0400, David Goulet wrote:
>> Hi everyone,
>>
>> For those who don't know, I've been working on a new version of Torsocks
>> in the last three weeks or so.
>>
>> https://lists.torproject.org/pip
Hi everyone,
For those who don't know, I've been working on a new version of Torsocks
in the last three weeks or so.
https://lists.torproject.org/pipermail/tor-dev/2013-June/004959.html
I just wanted to give a quick status report on the state of the development.
The DNS resolution is working fo
Matthew Finkel:
> On Sun, Jun 09, 2013 at 04:52:45PM -0400, David Goulet wrote:
>> Hi everyone,
>>
>
> Hi David!
>
>> I'm posting here the small design document I've made for the Torsocks locking
>> mechanism.
>>
>> I'm lookin
Hello! Comments below.
warms0x:
> (snip!)
>
>>> 4) One of the biggest technical issues is that it's not thread safe and
>>> fixing it right now would add an important impact on performance adding
>>> locks to multiple global data structures. A clean rewrite would allow to
>>> take into account th
re if any are needed after this thread is done
with.
https://github.com/dgoulet/torsocks/blob/rewrite/doc/proposals/01-Thread-safe-design.txt
Thanks people!
David
Date: 09/06/2013
Author: David Goulet
Contributors:
* Mathieu Desnoyers
This document details the design of torsocks locki
Of what I can see, proxychains and tsocks have not been updated since
2006 and 2002 (http://sourceforge.net/projects/proxychains/). I'm not
sure how "alive" these projects are.
Torsocks is of course Tor centric so it can be aware of different things
like what Ian talked about which is to use Optim
Fabio Pietrosanti (naif):
> On 6/4/13 2:08 PM, Ian Goldberg wrote:
>> David,
>>
>> Does the current version of torsocks support Optimistic Data? That
>> saves a round trip through the Tor network, and makes things snappier.
>> Tor clients, servers, and recently the Tor Browser now support it.
Rig
Mike Perry:
> David Goulet:
>
>> Hi everyone,
>>
>> About a week ago I've sent an email to the Torsocks maintainers to
>> address some concerns I had about important issues of the current code
>> base. For the reasons found below, I proposed a rewrite th
Hi everyone,
About a week ago I've sent an email to the Torsocks maintainers to
address some concerns I had about important issues of the current code
base. For the reasons found below, I proposed a rewrite that I am
willing to do and submit it to the community once I feel ok with it.
After some
LXE81lm0zpTRUWlM52HawyD
lGVBqMRf/V+F/g8EFqGpyZ3drs9o3+uNhY7/+qdSY6IhWJGUfyL7vrwYSk1/yuBf
RWBFE050zLhd9QwCARCoxb0E+oGsh/Z6hq8NgcDxba28Z2II+azE3KrNkwAuUnob
N/6gUd8ceWpyXmFgCpf3MJLNqZKOcYXax2LFA+ocQdQ368VD+Lq8jqPXfR62Npr4
Ujhp9i2REALbbV6dOmxBVdytK9v2NfFGZIXp9n5onU8/Ym9a8fg0ZvUk+i5bwb+6
eOCYeLeVe7yNK8yzxnk6J8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi everyone,
I discovered, during a presentation at this year LinuxCon in San
Diego, the problem of "bufferbloat" which is encountered in network
bottlenecks.
https://en.wikipedia.org/wiki/Bufferbloat
http://www.bufferbloat.net/
There is been a go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12-02-03 02:46 AM, Mike Perry
> Either way, it sounds like good sense to make sure we have the option to
> say to people "Omg, you hit that crazy crash under heavy crypto load?
> Try building with --disable-non-determinism this time."
Haha! I'll re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12-01-31 03:08 PM, Watson Ladd wrote:
> On Tue, Jan 31, 2012 at 1:46 PM, David Goulet wrote:
> Hi everyone,
>
> To help the tor project, I'll contribute some of my spare time to improve
> multithreading for the Tor code base.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12-01-31 03:42 PM, Nick Mathewson wrote:
> On Tue, Jan 31, 2012 at 2:46 PM, David Goulet wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi everyone,
>>
>> To help the tor project, I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
To help the tor project, I'll contribute some of my spare time to improve
multithreading for the Tor code base.
I've speak a bit with Nick M. and it seems the crypto lib is an important part
to begin with. The wiki page
(https://trac.tor
201 - 259 of 259 matches
Mail list logo
