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 569
    • Issues 569
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • 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
  • Merge requests
  • !6317

Teach dnssec-settime to read unset times that it writes

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Tony Finch requested to merge 3361-dnssec-settime-unset into main May 17, 2022
  • Overview 8
  • Commits 1
  • Pipelines 7
  • Changes 11

When there is no time in a key file, dnssec-settime will print "UNSET", but to unset a time the user must specify "none" or "never". This change allows "unset" or "UNSET" as well as "none" or "never". The "UNSET" output remains the same to avoid compatibility problems with wrapper scripts.

I have also re-synchronized the "Timing Options" sections of the man pages.

Closes #3361 (closed)

Edited May 17, 2022 by Tony Finch
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 3361-dnssec-settime-unset