Hi,
Maxim Kammerer wrote (22 Jan 2013 18:00:00 GMT) :
> So in summary, I am all for making leaked information homogeneous, but
> only if there is actual possibility of leaks.
I understand Liberté's smaller set of software and bottom-up design
might allow to go as far as questioning the possibility of leaks
altogether, but as far as Tails is concerned, I'd rather not bet we'll
be building and maintaining a perfect blacklist of every possible leak
forever, and have always up-to-date configuration and patches to fix
it all. I simply prefer not to take the risk. Therefore, I'm totally
fine with going the security in depth way, and making this
information homogeneous.
Before I call it a proposal, I'd like to see the next point clarified,
though:
> Otherwise, it hurts usability.
I'm sorry but I don't see how. Could you please elaborate?
(In Tails case, I think the major place where this information is
exposed to the end-user in the Terminal; to my eyes, anon@liberte,
amnesia@amnesia and user@host all look equally bad to me from
a usability perspective.)
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
