Uploaded image for project: 'OpenDNSSEC'
  1. OpenDNSSEC
  2. OPENDNSSEC-378

ods-enforcer key list output may need to be changed

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: Enforcer NG
    • Labels:
      None

      Description

      The output of the 'ods-enforcer key list' command is quite different to that from 'ods-ksmutil key list' in 1.4. We need to review this to see if we can make it more compatible.

      1.4 output:

      Keys:
      Zone: Keytype: State: Date of next transition:
      ods KSK ready waiting for ds-seen
      ods ZSK retire 2013-01-21 17:17:00

      1.4 has a verbose mode:

      SQLite database set to: /var/opendnssec/kasp.db
      Keys:
      Zone: Keytype: State: Date of next transition (to): Size: Algorithm: CKA_ID: Repository: Keytag:
      ods KSK ready waiting for ds-seen (active) 2048 8 98a275082b94eb2f207ef2ed334d572c SoftHSM 30857
      ods ZSK retire 2013-01-21 17:17:00 (dead) 1024 8 1625c7383e43ea9d93440ea3ca1ed661 SoftHSM 51274
      ods

      2.0 output:

      Database set to: /var/opendnssec/kasp.db
      Keys:
      Zone: Key role: DS: DNSKEY: RRSIGDNSKEY: RRSIG: Pub: Act: Id:
      example.com KSK hidden hidden hidden NA 0 0 8e4511a004a3cb49b942f1c1775a03c8
      example.com ZSK NA hidden NA rumoured 0 1 70b045a64c479947775a5eec1992c018
      key list completed in 0 seconds.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              yuri Yuri Schaeffer
              Reporter:
              sara Sara Dickinson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: