Feature: Command to initialize Rugged TUF repository w/ existing root metadata.

@rugged @commands-local @initialize @root-metadata @gitlab-161
Feature: Command to initialize Rugged TUF repository w/ existing root metadata.
  In order to host TUF metadata using an HSM-based root key
  As an administrator
  I need to initialize a TUF repo with existing root metadata.

  Scenario: Initialize repository using existing root metadata.
    Given I reset Rugged
    And local Rugged directories exist
    And I run "sudo sudo -u rugged cp -r features/fixtures/hsm_support/verification_keys/* /var/rugged/verification_keys/"
    And I run "sudo sudo -u rugged cp -r features/fixtures/hsm_support/signing_keys/* /var/rugged/signing_keys/"
    And I run "sudo sudo -u rugged cp -r features/fixtures/hsm_support/tuf_repo/* /var/rugged/tuf_repo/"
    And I run "sudo chmod -R 600 /var/rugged/signing_keys/snapshot/snapshot"
    And I run "sudo chmod -R 600 /var/rugged/signing_keys/targets/targets"
    And I run "sudo chmod -R 600 /var/rugged/signing_keys/timestamp/timestamp"
    And I record a reference hash of "/var/rugged/tuf_repo/metadata/1.root.json"
    When I run the Rugged command "rugged --debug initialize --local"
    And I should get:
      """
      debug: Loaded 'root' verification key for 'root' role.
      debug: Loaded 'root1' verification key for 'root' role.
      debug: Trying to initialize 'root' metadata from disk.
      debug: Loaded metadata for 'root' role from '/var/rugged/tuf_repo/metadata/1.root.json'.
      warning: Initialized 'root' metadata from disk.
      If you did not intend to initialize with existing 'root' metadata then delete '1.root.json' and re-run this command.
      """
    And I should not get:
      """
      debug: Loaded 'root' signing key for 'root' role.
      debug: Loaded 'root1' signing key for 'root' role.
      debug: Did not find 'root' metadata on disk to load.
      """
    Then file "/var/rugged/tuf_repo/metadata/1.root.json" has not changed
    And the file "/var/rugged/tuf_repo/metadata/2.root.json" does not exist
    When I run the Rugged command "rugged validate metadata"
    Then I should get:
      """
      Metadata for the 'root' role is valid.
      Metadata for the 'timestamp' role is valid.
      Metadata for the 'snapshot' role is valid.
      Metadata for the 'targets' role is valid.
      """
    And I should not get:
      """
      error: Metadata for the 'root' role is not valid.
      error: Metadata for the 'timestamp' role is not valid.
      error: Metadata for the 'snapshot' role is not valid.
      error: Metadata for the 'targets' role is not valid.
      """

1 scenario (1 passed)
17 steps (17 passed)

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Rugged TUF Server is a trademark of Consensus Enterprises.