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 you're on the old version like me. Comrade Ringo Kamens
On 8/10/07, Kyle Williams <[EMAIL PROTECTED]> 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. > > > On 8/10/07, Florian Reitmeir <[EMAIL PROTECTED]> wrote: > > 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 compile from source or > > > disable your controlport and wait out the storm until a new version is > > > released. Is the package maintainer busy or..? > > > Comrade Ringo Kamens > > > > the last security issue, is no issue on debian linux, because on debian > Tor > > can't write its config file. And the packager is on holidays in > Finowurth, > > unil sunday. > > > > -- > > Florian Reitmeir > > > >
