Re: [tor-dev] Upcoming Onionoo version 3.1 removes "family" field from details and stops returning code 500 when serving stale data

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/01/16 10:25, Karsten Loesing wrote: > Hello Onionoo users, > > the upcoming Onionoo [0] version 3.1 will contain two minor > changes that are worth announcing in advance: > > - Details documents will not contain a "family" field anymore but >

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

Spencer: > >Nick Mathewson: > >proposals sit around for a long time > > > > Is there a summarized visualization of these, or is it sifting through > emails and tickets? Proposals are all kept in the “torspec” Git repository: https://gitweb.torproject.org/torspec.git/tree/proposals Once in a

Re: [tor-dev] Revisiting Proposal 246: Merging Hidden Service Directories and Introduction Points

On 16 Jan (16:21:30), John Brooks wrote: > > > On Jan 16, 2016, at 4:52 AM, George Kadianakis wrote: > > > > Yes, I think I agree with this evaluation for now. Seems prop246 is more > > complicated than we can handle, and we should probably postpone it, except > > if > >

[tor-dev] Entry/Exit node selection

What threat is Tor trying to defeat? Region locking or nation states? If the former, then great, select an exit country, or just use a VPN. If the latter, perhaps that actual threat profile should be taken into account. Is there any reason why Tor doesn't select exit nodes which are as close as

[tor-dev] ENGINE_get_default_ECDx missing?

Seems these two OpenSSL functions: ENGINE_get_default_ECDSA() ENGINE_get_default_ECDH() have been dropped; in util/libeay32.num: ... ENGINE_get_default_ECDH 33871_1_0 NOEXIST::FUNCTION: ENGINE_get_default_ECDSA36621_1_0 NOEXIST::FUNCTION: ...

Re: [tor-dev] ENGINE_get_default_ECDx missing?

On Mon, 18 Jan 2016 19:43:37 +0100 Gisle Vanem wrote: > Isn't OpenSSL 1.1.0 supported yet? Scratching head... We fix it when it breaks but it's not a high priority or something currently tested against. When 1.1.0 has a stable release, this will change, but people building

Re: [tor-dev] Entry/Exit node selection

On Mon, 18 Jan 2016 13:53:47 -0400 "Evan d'Entremont" wrote: > Is there any reason why Tor doesn't select exit nodes which are as > close as possible to the intended host? The generic way to ask this question is "AS-aware path selection". One big general issue is, "there

Re: [tor-dev] Entry/Exit node selection

On Mon, 18 Jan 2016 14:26:04 -0800 Spencer wrote: > > > > Evan d'Entremont: > > ... select exit nodes ... > > > > It would be best if people could select their own path (: You can with the control port. Moving it to a first class feature would be a terrible idea

[tor-dev] Entry/Exit node selection

Hi, > > Evan d'Entremont: > ... select exit nodes ... > It would be best if people could select their own path (: Wordlife, Spencer ___ tor-dev mailing list tor-dev@lists.torproject.org

Re: [tor-dev] Entry/Exit node selection

> On 19 Jan 2016, at 04:53, Evan d'Entremont wrote: > > What threat is Tor trying to defeat? Region locking or nation states? If the > former, then great, select an exit country, or just use a VPN. If the latter, > perhaps that actual threat profile should be taken

Re: [tor-dev] Always up-to-date HSTS preload list for Tor?

Hi, Ivan Ristic: > Dear Tor developers, > > My SSL Labs server test has a feature where it checks for preloaded HSTS > in Chrome, IE, Firefox, and Tor. > > You can see it near the bottom of this report, for example (under "HSTS > Preloading"): > >