On 27-01-13 22:46, Jacob Appelbaum wrote:
> I've merged this patch and as a result, I've also taken the liberty of
> cleaning up some autotools noise and bumping the version number.
>
> Thus, I am declaring the following tar.gz to be the RC for 1.3:
>
> https://people.torproject.org/~ioerror/src
On Sun, Jan 27, 2013 at 4:46 PM, Jacob Appelbaum wrote:
[...]
>
> I've merged this patch and as a result, I've also taken the liberty of
> cleaning up some autotools noise and bumping the version number.
>
> Thus, I am declaring the following tar.gz to be the RC for 1.3:
>
> https://people.torpro
Oscar Koeroo:
> Hi,
>
> I've created trac ticket[1] #8063.
>
> The torsocks script has an option "on" which did't work and in the current
> state I'm curious on which shell it did work :-)
>
> The patch is included and only affects the src/torsocks.in file with a
> oneliner. More details are inc
Hi,
I've created trac ticket[1] #8063.
The torsocks script has an option "on" which did't work and in the current
state I'm curious on which shell it did work :-)
The patch is included and only affects the src/torsocks.in file with a
oneliner. More details are included on the ticket.
O
Hi,
Is there any info from current Tor QA use?
I am trying to reproduce a Tor bug that causes a Windows-based Tor node
to crash (BSOD). The bug needs lots of Tor traffic going through the
node for it to crash.
I am looking for information on the safest way to diagnose a crashing
Tor node, w
intrigeri:
> Hi,
>
> Jacob Appelbaum wrote (27 Jan 2013 04:16:30 GMT) :
>> I think this also includes all of the pending Debian fixes
>
> I confirm.
>
Great, I think that means that we're ready to tag a torsocks release
unless someone shouts that we have a regression!
All the best,
Jake
_
Ian Goldberg:
> On Sun, Jan 27, 2013 at 04:37:55PM +, Jacob Appelbaum wrote:
>> Hi Ian,
>>
>> This version of Torsocks is the initial bug clean up that will lead us
>> into fixing larger issues such as that one. We think this is a good idea
>> as a few of those bugs are quite a lot of work and
On Sun, Jan 27, 2013 at 04:37:55PM +, Jacob Appelbaum wrote:
> Hi Ian,
>
> This version of Torsocks is the initial bug clean up that will lead us
> into fixing larger issues such as that one. We think this is a good idea
> as a few of those bugs are quite a lot of work and there were many
> ou
Ian Goldberg:
> On Sun, Jan 27, 2013 at 04:16:30AM +, Jacob Appelbaum wrote:
>> Hi,
>>
>> Nick and I have been working on a torsocks release. At this point, I
>> think we're at the point where we want to declare a release candidate
>> which if it has no blockers, we'll likely call it a release.
I tried this branch on a PPC Debian stable (squeeze) machine, and it
appears to work fine. I saw no DNS requests, see no warnings about
res_ methods and at least one .onion worked.
(And no compiler warnings, woo!)
--
meejah
___
tor-dev mailing list
Hi,
Jacob Appelbaum wrote (27 Jan 2013 04:16:30 GMT) :
> I think this also includes all of the pending Debian fixes
I confirm.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.as
On Sun, Jan 27, 2013 at 04:16:30AM +, Jacob Appelbaum wrote:
> Hi,
>
> Nick and I have been working on a torsocks release. At this point, I
> think we're at the point where we want to declare a release candidate
> which if it has no blockers, we'll likely call it a release. I think
> we'll cal
12 matches
Mail list logo
