Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 606
    • Issues 606
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #2406
Closed
Open
Issue created Jan 22, 2021 by Matthijs Mekking@matthijs🏡Developer

kasp: look at Inactive/Delete when initializing state files

The internal BIND keymgr tries to initialize legacy keys (keys without a state file). If no state file is present it is going to assume the keys in use are actively being used for signing (so setting everything to rumoured or omnipresent, depending on the time).

Initializing the state files currently does not look at the Inactive and Delete time. So I agree that we can add logic such that when the Inactive time has passed set the key goal to hidden and ds/krrsig/zrrsig to unretentive, and when the Delete time has passed set the everything to hidden.

Assignee
Assign to
Time tracking