In order to successfully issue end entity (server/client) certificates, it must be possible to initialise a CA hierarchy. Hierarchy initialisation should be kept as simple as possible.

The following should be done:

• Implement initialisation command.
• Initialisation command should:
  • Set-up the necessary directories.
  • Generate the necessary CA private keys.
  • Issue the necessary CA certificates.
  • Provide user with information on what has been created.
• Initialisation command should support the following options:
  • Base name for the issued CA certificates. Base name should default to current working directory name.
  • CA hierarchy depth. Default should be 1 (just the root).
• Initialisation command should be implemented with the following constraints in mind:
  • Don't be destructive. If the hierarchy has already been created, show a warning to user, instructing them to remove directory first, and do not overwrite any data.
  • Artifacts should be stored within a sub-directory called .gimmecert.
  • CA certificate subject DN should be of format CN=BASE Level N CA, where BASE is the base name, and N is the level of CA (level 1 for root, level 2 for CAs signed by root etc).
• Documentation should cover:
  • Simple command use, without providing any parameters.
  • Complex command use, showing how to specify custom base name and hierarchy depth.
  • Directory and file layout structure of generated artifacts.