On 03/27/2009 06:31 AM, Kyle Hamilton:
The original idea was how to improve Thunderbird's existing abilities to
work with crypto and deliver security. If you read my proposal carefully
you will see I very carefully separated the crypto/secure email part from
the certificates part.
The overall idea I proposed was not really designed to prevent SSCs,
it was designed to give users the ability to easily opt into the CA
strategy at class 1 (email address receipt ability verification).
Looking back on it, I see that I didn't make that as clear as I
otherwise could have.
I'm fully supporting such an attempt if it should take of.
Which is to say, the original proposal was to improve email security. It was
not to improve the use of client certificates. The latter is both foolish
as an objective, and is also a limiting drain on security for email for
users, especially for Thunderbird's typical users, if taken as the only
objective.
Having someone who represents a CA in the discussion will almost
certainly entail discussion and promotion of products that the CA
offers.
Not really, besides the promotional effect and exposure of the
organization name amongst a bunch of other CAs we are talking about free
services here (perhaps in the hope that somebody upgrades). However I
know to distinguish between the requirements of Mozilla and that of my
company in this respect. Also I'd agree with you if it would benefit my
company exclusively, which is certainly not the case.
--
Regards
Signer: Eddy Nigg, StartCom Ltd.
Jabber: start...@startcom.org
Blog: https://blog.startcom.org
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
