Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 566
    • Issues 566
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • 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
  • #2628
Closed
Open
Issue created Apr 12, 2021 by Matthijs Mekking@matthijs🏡Owner

Key generation should check for key id conflicts with newly created keys too

Job #1632735 failed for 0ebacc63:

I:kasp:check number of keys for zone ecdsa256.kasp in dir ns3 (203)
I:kasp:error: bad number of key files (2) for zone ecdsa256.kasp (expected 3)
I:kasp:check key id 26891
I:kasp:check key id 22631
I:kasp:KEY1 ID 22631
I:kasp:KEY2 ID no
I:kasp:error: No KEY2 found for zone ecdsa256.kasp
I:kasp:KEY3 ID 26891
I:kasp:failed

This test creates two new keys with the same key ID. The keymgr checks for conflicts, but only with already existing keys.

Assignee
Assign to
Time tracking