Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 582
    • Issues 582
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 110
    • Merge Requests 110
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #1151

Closed
Open
Opened Jul 21, 2019 by Ondřej Surý@ondrejOwner

Inconsistent usage of stdout vs stderr in signing tools

Both dnssec-signzone and dnssec-verify print some information to stdout and some to stderr. This looks like an unfinished legacy code and needs to be fixed, so normal run information are print to stdout, and only real errors (and warnings) go to stderr.

Assignee
Assign to
BIND 9.15.3
Milestone
BIND 9.15.3 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/bind9#1151