On Tuesday, 4 April 2017 04:18:41 UTC+1, Jakob Bohm wrote: > So why does Mozilla want disclosure and not just a blanket X on a form > stating that all SubCAs are adequately audited, follow BRs etc.?
Not speaking for Mozilla of course, but as a fan of disclosure provisions: Mandating disclosure averts hypocrisy. Hypocrisy is poisonous, so we should try to reduce it when doing so has a reasonable cost. Consider you're Honest Achmed. You see a business opportunity for your CA. It will make a lot of money, but you suspect most people will think it is wrong. Historically, all you needed to do was persuade yourself (and maybe a few other key personnel) that it's actually fine, and you're golden. If other people find out what you did that's a problem, but you can put that problem off until it happens. Under mandatory disclosure, you have three options right up front: You can persuade everybody else that it's fine too, in which case it really is fine; You can abandon the opportunity because the risk of disapproval is unacceptable; You can do it anyway and hope for forgiveness, risking absolute distrust. Now, a mandatory approval requirement would strengthen this by eliminating that last option. But it does so at an enormously greater cost as you've identified. Mandatory disclosure gets us most of the benefit, at a much lower cost. _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

