Background
CAcert uses roots as described at Structure of Roots and many other places. Because the existing roots have been deemed to be Audit Fail here, we have to create new ones.
Work List
This then means we need these things:
- technical organisation of roots:
Roots/Structure describes the hierarchy and relationship between the roots
Roots/Contents describes the internal fields in each Roots.
- ceremony for creation of root (s)
Roots/CreationCeremony is open as a place to develop this need
Roots/TechScript is where the geeky arcania can be collected
- storage securely on signing server
- escrow root securely for disaster recovery
Roots/EscrowAndRecovery is open for jotting notes...
- finally, when all is good, start the rollout procedure
Roots/RolloutProcedure is open for jotting notes...
Note that as we decide on the way to do this, the process should be transferred to the wip CPS and the wip Security Manual. These pages are the works-in-progress of the New Roots Task Force.
Proposals
- Creation an offine root to be stored securely (eg board controlled safety deposit box)
- Creation of sub-roots for different CAcert functions:
- Web of Trust (eg CAP)
- Remote Assurance (eg RAP)
- Organisation Assurance (eg OAP)
Creation of sub-roots for assured organisations (from which they can issue certificates)
Root cert chain testing
Please have a look on Roots/TestNewRootCerts to help testing the new model of root certificates.
Teams
Root Key Task Force is CAcert Sub-Committee installed by board motion m20081008.1 see Board decision list 2008. Task Force has the following members: Guillaume Rogmany, Teus Hagen, auditor (Ian Grigg) and advisor (Philipp Gühring).
The following teams:
Root Key Task Force |
software configuration and scripting |
|
|
Guillaume Rogmany |
in charge |
|
Teus Hagen |
|
Security Evaluation |
Philipp Gühring |
remote |
Crytical Systems |
system admin |
|
|
Wytze van der Raay |
in charge |
|
Mendel Mobach |
assists |
Oophaga |
servers and physical security |
|
|
Rudi Engelbertink |
in charge |
|
Rudi van Drunen |
|
|
Hans Verbeek |
|
Auditor |
Ian Grigg |
in charge |
Press & PR |
press contacts and news |
|
|
Maurice Kellenaers |
in charge |
|
Henrik Heigl |
|
Planning
Timeline
Roots/20081128 creation of Top-level root and 2 subroots (Member & Assured).
HAR2009 may be the next chance to test and/or to create additional subroots.
TO DO
Before activating the signing with the two new Sub-Root keys the new keys will be tested by Philipp Gühring and others. The signed certificates will be tested for acceptance by different browsers (Mozilla, Internet Explorer, Opera, Safari, etc.) and key managers.
When policies have been accepted for the key signing (CPS) the new Sub-Root keys can be applied for signing.
Only the Sub-Root keys generated on this Key Generation event will then be used for the audit completion and if the audit is successful will be subjected for CA Root Key inclusion.