Hi all,
I have (since last week) two installations of the alpha browsers, both on
win7. The update of yesterday failed for both of them, first saying that
the incremental update could not be applied, then the full update couldn't
be either ('The Update could not be installed (patch apply failed)')
On Mon, 22 Jan 2018 13:33:31 +, Mirimir wrote:
...
> But it would be very cool if its vulnerabilities were clearly disclosed.
> On the download page. There's already disclosure (but maybe not explicit
> enough) that Tor isn't secure against global adversaries. So why not
> disclosure that Tor b
Andreas Krey:
> Hi all,
>
> I have (since last week) two installations of the alpha browsers, both on
> win7. The update of yesterday failed for both of them, first saying that
> the incremental update could not be applied, then the full update couldn't
> be either ('The Update could not be instal
On Thu, 25 Jan 2018 11:40:00 +, Georg Koppen wrote:
...
> Could you enable update logging (with `app.update.log` set to `true`)
> and check the the browser console whether there is any error visible? If
> so, what is it complaining about?
Fresh install, no config change, except for the above (
Andreas Krey:
> On Thu, 25 Jan 2018 11:40:00 +, Georg Koppen wrote:
> ...
>> Could you enable update logging (with `app.update.log` set to `true`)
>> and check the the browser console whether there is any error visible? If
>> so, what is it complaining about?
>
> Fresh install, no config chang
On Thu, 25 Jan 2018 13:22:00 +, Georg Koppen wrote:
...
> without issue to 8.0a1 (both with an incremental and a full update). Hrm.
'Cannot reproduce'.
I filed #25023 for the alpha/current discrimination.
(Didn't find a good component, though.)
- Andreas
--
"Totally trivial. Famous last wo
Hi, all!
There's a new alpha Tor release! Because it's an alpha, you should
only run it if you're ready to find more bugs than usual, and report
them on trac.torproject.org.
The source code is available from the usual place on
www.torproject.org; if you build Tor from source, why not give it a
t
meek-azure seems to be having issues. Reproduced on multiple machines. Any
information?
meek-client.txt output:
listening on 127.0.0.1:X
status code was 504, not 200; trying again after 30 seconds (9)
Tor Log output:
[NOTICE] Opening Socks listener on 127.0.0.1:9150
[NOTICE] Bootstrapped
