Hi,

[email protected] wrote (22 Jan 2015 01:00:23 GMT) :
> You dont even bother to use https, why may i ask?

FYI this style of questioning does not exactly motivate me to spend
more time on this discussion.

I'm pretty sure that I've explained at length already, earlier in this
thread, the time constraints we have and our current priorities on the
infrastructure front.

> At least with an onion address we would have an additional easily identifable 
> point
> of reference, the onion address,

I'm personally not able to "easily identify" a .onion address.

> The private key to the onion would serve as a second key that you
> could secure and use to authenticate your identities in the case of
> a breach.

Indeed, this would be useful. And now we face another problem.

Either (if the .onion becomes the only download option): how users are
supposed to download and trust the Tor Browser many of them would have
to install first, before being able to download Tails from a .onion.

Or (if the .onion is added to the available download options): how do
we integrate this choice in our installation process doc?
It's a well-known problem that Tails is too hard to install initially
for most potential users, and we want to fix that.

Cheers,
--
intrigeri
_______________________________________________
tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
To unsubscribe from this list, send an empty email to 
[email protected].

Reply via email to