• Roots
• NewRootsTaskForce

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:

1. technical organisation of roots:

   • Roots/Structure describes the hierarchy and relationship between the roots

   • Roots/Contents describes the internal fields in each Roots.

2. 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

3. storage securely on signing server
4. escrow root securely for disaster recovery

   • Roots/EscrowAndRecovery is open for jotting notes...

5. 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.

Planning

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 advisory (Philipp Gühring).

Date and Location

The Root Key Generation (One Root Key and 2 sub-rootkeys) has been scheduled on 27th and 28th of November in Holland.

Budgets

hotel

Hotel Tiel or Grubbenvorst (teus/home).

work location

Grubbenvorst (teus/home) or Mobach/Echteld?