Re: [tor-dev] [Tails-dev] Tails vs the capacity of the Meek bridges

2020-03-24 Thread anonym
Iain Learmonth: > Hi, > > On 20/03/2020 15:30, sajolida wrote: >>> In Tails' threat model it is assumed that adversaries monitor the default >>> bridges provided by the Tor Browser, and that our users want to avoid >>> detection of that, so we are not interested in adding the default bridges

Re: [tor-dev] Tails vs the capacity of the Meek bridges

2020-03-24 Thread anonym
David Fifield: > On Fri, Mar 20, 2020 at 11:51:41AM +0100, anonym wrote: >> tl;dr: if Tails makes it too easy to use Meek bridges, could it overload the >> current set of Meek bridges? > > The default meek bridge is already overloaded, unfortunately. Ack. Tails will then *

[tor-dev] Tails vs the capacity of the Meek bridges

2020-03-20 Thread anonym
Hi, tl;dr: if Tails makes it too easy to use Meek bridges, could it overload the current set of Meek bridges? First some background: during startup Tails can be told to start Tor Launcher so users can e.g. configure any bridges they want. So far we have not provided any pre-configured

Re: [tor-dev] Acceptable clock skew in tor 0.4.1

2019-11-14 Thread anonym
George Kadianakis: > An unfortunate exception here is v3 onion services: v3 onion services > only tolerate skews of maximum ±3 hours [1] but in most cases even > tighter than that. This is to assure that v3 clients and services have a > recent and accurate view of the network. In theory all of Tor

[tor-dev] Let's build Tails 3.2~alpha2 instead! [Was: Help us build Tails 3.2~alpha1 build reproducibly]

2017-09-08 Thread anonym
Hi (yet) again, It turns out there's a serious problem with Tails 3.2~alpha1 so it actually depends on *when* you build it -- the longer you wait, the more it will diverge from the "canonical" 3.2 that was built yesterday (in short: I forgot to freeze which APT repo snapshot to use when

Re: [tor-dev] [Tails-dev] Help us build Tails 3.2~alpha1 build reproducibly

2017-09-08 Thread anonym
anonym: > ### ... and the checksums differ (i.e. reproduction failed). > [...] > sudo apt -o APT::Install-Suggests="true" \ > -o APT::Install-Recommends="true" \ > install diffoscope -t stretch-backports It was reported to us th

Re: [tor-dev] Help us build Tails 3.2~alpha1 build reproducibly

2017-09-08 Thread anonym
anonym: > git checkout 3.2~alpha1 Oops! That should be: git checkout 3.2-alpha1 In other words, the "~" (tilde) should be a "-" (dash). Sorry for the inconvenience! Cheers! signature.asc Description: OpenPGP digital signature

[tor-dev] Help us build Tails 3.2~alpha1 build reproducibly

2017-09-07 Thread anonym
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Tails and Tor contributors, dear Reproducible Builds community, We have sent out a first call [1] for testing to build Tails 3.1 reproducibly and we have received some build reports. Thank you very much for your help! We have since then tried

Re: [tor-dev] Control-port filtering: can it have a reasonable threat model?

2017-04-10 Thread anonym
Nick Mathewson: > Hi! > > As you may know, the Tor control port assumes that if you can > authenticate to it, you are completely trusted with respect to the Tor > instance you have authenticated to. But there are a few programs and > tools that filter access to the Tor control port, in an

Re: [tor-dev] "firefox --app" for meek-http-helper

2017-03-29 Thread anonym
Georg Koppen: > David Fifield: >> On Sun, Mar 26, 2017 at 02:28:00PM +0000, anonym wrote: >>> Tails uses the Tor Launcher shipped in Tor Browser, but it's run as a >>> stand-alone XUL application (`firefox --app ...`), so the *web* >>> browser isn't started

Re: [tor-dev] GSOC 2017: Proposal for anon-connection-wizard

2017-03-26 Thread anonym
irykoon: > Currently, the Tor Launcher is shipped with the Tor Browser Bundle and > heavily relies on the Tor Browser for its implementation. These facts > cause using Tor Launcher without having the Tor Browser impossible. I > agree with the whonix core developer Patrick Schleizer that "the Tor >

Re: [tor-dev] Onionboat: Using Docker for easy hidden services

2016-06-14 Thread anonym
George Kadianakis: > Hello segfault, > > someone linked me to this today: > > https://nonconformity.net/2016/06/10/onionboat-using-docker-for-easy-tor-hidden-services/ >https://github.com/jheretic/onionboat > > Forwarding it because of being potential relevant to your GSoC project (Tails

Re: [tor-dev] [RELEASE] Torsocks 2.1.0

2015-05-28 Thread anonym
On 05/27/2015 09:19 PM, David Goulet wrote: - IsolatePID is a new option that will make torsocks set the SOCKS5 username and password automatically to provide isolation on Tor side. You can use this with the -i,--isolate command added or TORSOCKS_ISOLATE_PID env. variable. Perhaps I'm

Re: [tor-dev] [RELEASE] Torsocks 2.1.0

2015-05-28 Thread anonym
On 05/28/2015 03:11 PM, Yawning Angel wrote: Ah, this is a matter of the feature is explained in a simple manner in the abbreviated changelog. What the flag actually does is: * Username set to 'torsocks-' PID ':' unixTime Thanks for the clarification! This indeed sounds a lot better.

Re: [tor-dev] [tor-talk] heartbleed: ETA for tor release(s) that blacklist affected directory authority keys? (#11464)

2014-04-23 Thread anonym
21/04/14 12:27, Nusenu wrote: Hi, the code to blacklist heartbleed affected tor directory authority keys has been merged about a week ago [1]. Do you have an ETA on when you are going to release it (tor and TBB packages)? As the release manager for the Tails 1.0 release I'm also

Re: [tor-dev] [Tails-dev] Working on GUI

2012-11-08 Thread anonym
07/11/12 18:41, intrigeri wrote: Hi, Damian Johnson wrote (06 Nov 2012 23:31:02 GMT) : Runa A. Sandvik wrote (06 Nov 2012 22:44:03 GMT) : Actually, both Tails and the Tor Browser Bundle could benefit from a usability study. Thank you, Runa, for mentioning Tails here. Seconded! Thank