Re: [tor-dev] Load Balancing in 2.7 series - incompatible with OnionBalance ?

2015-10-20 Thread Alec Muffett
typo: > alecm: and this persists for up to 24h, even though the outage was only 10 > minutes Also, I neglected to observe that linear polling of A-E seeking a descriptor suggests A will be hammered whilst J is nearly idle. Some entropy in IP selection would be a good thing. -a — Alec Muf

[tor-dev] Load Balancing in 2.7 series - incompatible with OnionBalance ?

2015-10-20 Thread Alec Muffett
So I’ve just had a conversation with dgoulet on IRC, which I will reformat and subedit here as a conversation regarding OnionBalance and issues in 2.6 and 2.7 when a recently rebooted HS publishes a fresh descriptor: […] alecm: consider OnionBalance which - being a bunch of daemons on a bunch o

Re: [tor-dev] Effect of padding on end to end correlation false positive rate

2015-10-20 Thread grarpamp
On Fri, Oct 16, 2015 at 3:22 PM, s7r wrote: > I am describing something like a Sybil attack where the adversary runs > relays, gets lucky and is selected in a certain position of a certain > Does this change with padding? If yes, how? > [1]: https://blog.torproject.org/blog/traffic-correlation-us

Re: [tor-dev] adding smartcard support to Tor

2015-10-20 Thread Razvan Dragomirescu
Yes, that's precisely the point - if the card is stolen, the service is stolen with it. I'm not trying to prevent that, I'm trying to _tie_ the service to the card - whoever has the card runs the service. If you see that the card is gone, you know your service is gone too. If the card is still ther

Re: [tor-dev] adding smartcard support to Tor

2015-10-20 Thread grarpamp
On Tue, Oct 20, 2015 at 3:05 PM, Ivan Markin wrote: > No, I will be secure. An adversary could sniff your PIN and sign > whatever they want to, true. But revealing the PIN != revealing the key. > In this case your identity key is still safe even if your PIN is > "compromised". Yes the private key

Re: [tor-dev] Feedback on CollecTor web redesign

2015-10-20 Thread Damian Johnson
> I agree with David. I like the change, especially the table (nice > work!). Though a lot of the text is well into TL;DR territory. If the > welcome message could be half the size that would help, and the > formats have some redundancy. For instance, hidden service descriptors > and bridge pool an

Re: [tor-dev] Feedback on CollecTor web redesign

2015-10-20 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/10/15 21:36, David Fifield wrote: > On Tue, Oct 20, 2015 at 09:31:38PM +0200, Karsten Loesing wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> Hi devs, >> >> I just finished a redesign of the CollecTor website and would >> appreci

Re: [tor-dev] Feedback on CollecTor web redesign

2015-10-20 Thread Damian Johnson
I agree with David. I like the change, especially the table (nice work!). Though a lot of the text is well into TL;DR territory. If the welcome message could be half the size that would help, and the formats have some redundancy. For instance, hidden service descriptors and bridge pool annotations

Re: [tor-dev] Feedback on CollecTor web redesign

2015-10-20 Thread David Goulet
On 20 Oct (21:31:38), Karsten Loesing wrote: > Hi devs, > > I just finished a redesign of the CollecTor website and would > appreciate your feedback: > > https://metrics.torproject.org/index2.html I think you mean: https://collector.torproject.org/index2.html :) I like it. There is quite a b

Re: [tor-dev] Feedback on CollecTor web redesign

2015-10-20 Thread David Fifield
On Tue, Oct 20, 2015 at 09:31:38PM +0200, Karsten Loesing wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi devs, > > I just finished a redesign of the CollecTor website and would > appreciate your feedback: > > https://metrics.torproject.org/index2.html This URL is 404 for me.

[tor-dev] Feedback on CollecTor web redesign

2015-10-20 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi devs, I just finished a redesign of the CollecTor website and would appreciate your feedback: https://metrics.torproject.org/index2.html For reference, the old CollecTor website is still available here: https://metrics.torproject.org/index.h

Re: [tor-dev] adding smartcard support to Tor

2015-10-20 Thread Ivan Markin
grarpamp: > Yes if you intend to patch tor to use a smartcard as a > cryptographic coprocessor offloading anything of interest > that needs signed / encrypted / decrypted to it. The card > will need to remain plugged in for tor to function. As I said before, only thing that actually needs to be pr

Re: [tor-dev] adding smartcard support to Tor

2015-10-20 Thread grarpamp
You mentione... > I have Tor running on the USBArmory by InversePath ( > http://inversepath.com/usbarmory.html ) and have a microSD form factor card > made by Swissbit ( > www.swissbit.com/products/security-products/overwiev/security-products-overview/ > ) up and running on it. Good that USBarmor

Re: [tor-dev] adding smartcard support to Tor

2015-10-20 Thread grarpamp
On Sat, Oct 17, 2015 at 5:46 PM, Razvan Dragomirescu wrote: > Exactly, you ask the smartcard to decrypt your traffic (and sign data if > needed), it never tells you the key, it's a blackbox - it gets plaintext > input and gives you encrypted (or signed) output, without ever revealing the > key it'