Feature: Generated keys do not have deprecated `keyid_hash_algorithms` data.

@rugged @no-keyid_hash_algorithms @local @gitlab-192
Feature: Generated keys do not have deprecated `keyid_hash_algorithms` data.
  In order to generate TUF-compliant keypairs
  As an administrator
  I need to ensure that keys do not include `keyid_hash_algorithms` data.

  Scenario Outline: Check that generated keys do not include `keyid_hash_algorithms`.
    Given I reset Rugged
    When I run the Rugged command "rugged --debug generate-keys --local --role <KEY>"
    Then I should get:
      """
      Looking for 'keyid_hash_algorithms' in public key at
      Found 'keyid_hash_algorithms' in public key at
      Deleting 'keyid_hash_algorithms' from public key at
      Re-writing public key at
      Looking for 'keyid_hash_algorithms' in private key at
      Found 'keyid_hash_algorithms' in private key at
      Deleting 'keyid_hash_algorithms' from private key at
      Re-writing private key at
      """
    Then I should not get:
      """
      Did not find 'keyid_hash_algorithms' in generated key.
      Please remove `rugged.tuf.key_manager._remove_keyid_hash_algorithms()`.
      """
    When I run "sudo cat /var/rugged/signing_keys/<KEY>/<KEY>"
    Then I should get:
      """
      keytype
      scheme
      keyid
      keyval
      """
    And I should not get:
      """
      keyid_hash_algorithms
      """
    When I run "cat /var/rugged/verification_keys/<KEY>/<KEY>.pub"
    Then I should get:
      """
      keytype
      scheme
      keyval
      """
    And I should not get:
      """
      keyid
      keyid_hash_algorithms
      """

    Examples:
      | KEY       |
      | root      |
      | targets   |
      | snapshot  |
      | timestamp |

4 scenarios (4 passed)
40 steps (40 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.