* on the Fri, Aug 10, 2007 at 04:12:21PM -0400, Ringo Kamens wrote:
As you know, a major security vulnerability was just patched with the
0.1.2.16 release. I have been using the noreply.org deb packages but
they didn't update to the newest version (at least not under amd64
feisty). If you are
On Fri, 10 Aug 2007, coderman wrote:
On 8/10/07, Ringo Kamens [EMAIL PROTECTED] wrote:
I think what he is saying (which might be true) is that tor doesn't
have the permissions to save the torcc.
there are some configurations that don't allow saving the config.
they are still vulnerable.
On Fri, 10 Aug 2007, Kyle Williams wrote:
This is not true. The affects of the bug are very sever, and it DOES NOT
require the config to be saved! An attacker could still cause you to loose
your anonymity.
UPDATE, UPDATE, UPDATE.
like i wrote before, you are only vunerable if you have the
@Mike: Good to know. I'll just use the etch version for now since
feisty isn't out.
Comrade Ringo Kamens
On 8/11/07, Florian Reitmeir [EMAIL PROTECTED] wrote:
On Fri, 10 Aug 2007, Kyle Williams wrote:
This is not true. The affects of the bug are very sever, and it DOES NOT
require the
As you know, a major security vulnerability was just patched with the
0.1.2.16 release. I have been using the noreply.org deb packages but
they didn't update to the newest version (at least not under amd64
feisty). If you are in my situation you can compile from source or
disable your controlport
By debian linux are we talking about all major debian-based distros
(IE ubuntu and it's variants)? How about non-debian based Linux
distros such as red-hat based ones? Good news.
Comrade Ringo Kamens
On 8/10/07, Florian Reitmeir [EMAIL PROTECTED] wrote:
On Fri, 10 Aug 2007, Ringo Kamens wrote:
for dapper everything seems to be fine, at least for x86 machines.
On 8/10/07, Ringo Kamens [EMAIL PROTECTED] wrote:
As you know, a major security vulnerability was just patched with the
0.1.2.16 release. I have been using the noreply.org deb packages but
they didn't update to the newest
On Fri, 10 Aug 2007, Ringo Kamens wrote:
As you know, a major security vulnerability was just patched with the
0.1.2.16 release. I have been using the noreply.org deb packages but
they didn't update to the newest version (at least not under amd64
feisty). If you are in my situation you can
This is not true. The affects of the bug are very sever, and it DOES NOT
require the config to be saved! An attacker could still cause you to loose
your anonymity.
UPDATE, UPDATE, UPDATE.
On 8/10/07, Florian Reitmeir [EMAIL PROTECTED] wrote:
On Fri, 10 Aug 2007, Ringo Kamens wrote:
As you
I think what he is saying (which might be true) is that tor doesn't
have the permissions to save the torcc. If this is the case, then
editing it while in operation won't do anything anyways because in
order to load the edited-torcc it must save it first. Just turn off
your controlport for now if
On 8/10/07, Ringo Kamens [EMAIL PROTECTED] wrote:
I think what he is saying (which might be true) is that tor doesn't
have the permissions to save the torcc.
there are some configurations that don't allow saving the config.
they are still vulnerable.
If this is the case, then
editing it
11 matches
Mail list logo
