Michael Ströder wrote: > Arshad Noor wrote: > >> So, if I understand this correctly, the primary difference >> between what this message contains and S/MIME is that they >> chose to use a proprietary format for securing the e-mail >> as opposed to an industry standard that has been around for >> nearly 2 decades and is implemented in every major MUA. >> >> Since they could have implemented the exact same business >> capability using S/MIME, it sounds like this scheme was >> created to only lock in merchants. Doesn't appear to add >> any new value to the field of security. >> > > I concur. From my point as a S/MIME user (and consultant) the Mozilla > developers should focus on improving the UI for certificate and S/MIME > handling instead of implementing such a proprietary mechanism. Yes, I second that!
-- Regards Signer: Eddy Nigg, StartCom Ltd. <http://www.startcom.org> Jabber: [EMAIL PROTECTED] <xmpp:[EMAIL PROTECTED]> Blog: Join the Revolution! <http://blog.startcom.org> Phone: +1.213.341.0390 _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
