(sent to both mozilla.governance and mozilla.dev.security.policy)
Hey all, I just discovered an odd state of affairs that could use some
clarification. I apologize for the TLDR email that follows, but this
requires some explanation. I cannot tell for sure who is the owner of
the relevant modules for Mozilla's certificate authority root list
policy and management. Specifically, there are two modules:
1. CA Certificate Policy
responsible for maintaining:
http://www.mozilla.org/projects/security/certs/policy/
2. CA Certificates
"Determine which root certificates should be included in Mozilla
software products and which trust bits should be set on them, and
evaluate requests from Certification Authorities (CAs) for inclusion of
new root certificates."
As I understand it, the first module is for making changes to the Policy
text itself, whereas the second is for day-to-day decisions about root
approvals. Who are the current owners and peers for these modules? The
wiki is inconsistent:
https://wiki.mozilla.org/Modules/Activities
CA Certificate Policy
Owner: Kathleen Wilson
Peers: Frank Hecker, Gervase Markham, Johnathan Nightingale
CA Certificates
Owner: Kathleen Wilson
Peers: Frank Hecker, Gervase Markham, Johnathan Nightingale
https://wiki.mozilla.org/Module_Owners_Activities_Modules
CA Certificate Policy
Owner: Frank Hecker
Peers: Kathleen Wilson
CA Certificates
Owner: Kathleen Wilson
Peers: Frank Hecker
It seems that Kathleen is definitely owner of the CA Certificates
module, and that Gerv and Jonathan are probably peers of both. However,
the actual owner of the CA Certificate Policy is unclear. Kathleen
herself said recently that "Frank is still the owner of Mozilla's CA
Certificate Policy":
https://groups.google.com/group/mozilla.dev.security.policy/browse_thread/thread/bed934bffdbf30de/02c3156ee063505d#f8276c156fa742d5
In August of 2010, Frank had proposed making Kathleen owner of the CA
Certificates module and peer (and maybe owner?) of the CA Certificate
Policy module:
https://groups.google.com/group/mozilla.governance/browse_thread/thread/76862f38c7ccb897/725bea39d18a1cd6
In the thread that followed, it was unclear to me what the final
decision was on ownership of the CA Certificate Policy, and the wiki
seems to reflect this ambiguity.
Despite the similarity of names between the two modules, I think that
there is a good reason why they were created separate. One deals with
the day-to-day administration of the root list (a very time consuming
task) and the other deals with setting the policy itself. Although they
closely inform each other, day-to-day administration tasks can often
consume all available time and distract from policy updates. It
probably often makes sense to have these owned by different people in
order to avoid blocking of one by the other, and even to create a bit
more of a firewall between the process of negotiating with CAs on
acceptable compliance and updates/interpretations of the text itself.
To that end, I think that it would be useful to acknowledge the fact
that Frank is, from a practical perspective, no longer an owner or a
peer of either of these modules (he left Mozilla in 2009 and he hasn't
posted to this list in more than a year). I think it is also useful to
acknowledge the benefit of having different module owners, and to move
toward a situation where that is the case. As such, regardless of who
is the actual current owner of the CA Certificate Policy module, I'd
like to propose a new peer who could add some great energy and perhaps
prove himself to be a good owner as well.
Thomas Lowenthal (tom@mozilla) has posted to m.d.s.p. in the past and
works on privacy and security policy at Mozilla. He's also got
experience with Tor and is an admirably paranoid guy:
https://twitter.com/#!/flamsmark
I propose that he be appointed as a peer to the CA Certificate Policy
module.