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

2015-10-15 Thread grarpamp 
On Tue, Oct 13, 2015 at 4:08 PM, Razvan Dragomirescu
 wrote:
> essentially, I want to be able to host hidden service keys on the card. I'm
> trying to bind the hidden service to a hardware component (the smartcard) so
> that it can be securely hosted in a hostile environment as well as
> impossible to clone/move without physical access to the smartcard.

The host will have both physical and logical access to your
process space, therefore you're compromised regardless
of where you physically keep the keys or how you acccess
them.

Though there are trac tickets you can search for involving
loading keys into tor controller via remote tunnel without need
to leave and mount or access physical devices in /dev.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Upcoming Onionoo version 3.0 will support searches by space-separated fingerprint

2015-10-15 Thread grarpamp 
On Wed, Oct 14, 2015 at 6:46 AM, Karsten Loesing  wrote:
> the upcoming Onionoo version 3.0 will support searches by
> space-separated fingerprint.
>
> "9695DFC35FFEB861329B9F1AB04C46397020CE31"
>
> "9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31"

Instead of continuing to backport and further embed useless
legacy formats, will someone please write the proposal to get
rid of the damn spaces. I've covered the reasons why at least
twice before. Thanks.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Upcoming Onionoo version 3.0 will support searches by space-separated fingerprint

2015-10-15 Thread Karsten Loesing 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 15/10/15 23:59, grarpamp wrote:
> On Wed, Oct 14, 2015 at 6:46 AM, Karsten Loesing
>  wrote:
>> the upcoming Onionoo version 3.0 will support searches by 
>> space-separated fingerprint.
>> 
>> "9695DFC35FFEB861329B9F1AB04C46397020CE31"
>> 
>> "9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31"
> 
> Instead of continuing to backport and further embed useless legacy
> formats, will someone please write the proposal to get rid of the
> damn spaces. I've covered the reasons why at least twice before.
> Thanks.

It seems that the introduction of ed25519 identities will allow us to
find a format that doesn't suffer from shortcomings like this one.  Be
sure to watch that process and raise your concerns while they can
still be considered.

At the same time this makes it less likely that somebody will touch
the current RSA identities.

All the best,
Karsten

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJWIJIJAAoJEJD5dJfVqbCr1PUH/16dYoTH3lFkLqSfhmWDNLDQ
yNYUBGB/3ro/Gn39l/1tc0+ZqgXcgtv5jvirdZ9wBrGNEzaOeEiiDcNXZpUrQ9g9
8QuPe+ERQmu/Hk20TmV0XtMh/nRpKVTWQrHBCOnIeXjhlVpyeAKUFRkUTXL5OQ3I
fLYkGAli8jG8M49N9KYxiv9y4lizQFraiDqetrat1vzgngLtd5gBSXLmb6dQNHbv
7pQ1U3K9RoQ6Ra/J09CT1Ms+xIwuOHzw2TIbaBxHvmV/TkqarjMNxiRCChq1xk9Y
NbaTgmaXtiPgMIR2AsM46vfmhVuGdzXCc7CtS9/yK/Udxa2lfVyTSJm57vneR2I=
=jOw3
-END PGP SIGNATURE-
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Trac priorities and severities

2015-10-15 Thread Damian Johnson 
Hi David. Personally I find the split severity and priority redundant
but that's fine (milestone, tor version, and other fields are only
applicable to core tor - it's easy to ignore yet another field).
However, in this case you made it mandatory by giving it a default.
Mind making priority optional?

Cheers! -Damian
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev