Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 530
    • Issues 530
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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 Projects
  • BINDBIND
  • Issues
  • #303

Closed
Open
Created May 31, 2018 by Ondřej Surý@ondrejOwner0 of 6 tasks completed0/6 tasks

Improve const correctness

@bind-team, this is 3 years old review of BIND code by Errata Security: https://blog.erratasec.com/2015/07/a-quick-review-of-bind9-code.html and he is right.

We need to start using const more extensively and internalise it when writing new code and doing reviews.

It is a long term goals, so we will just keep this open, and I'll list major components that should be reviewed:

  • libisc
  • libdns
  • libns
  • libisccfg
  • libiscccc
  • bin/named
Edited May 31, 2018 by Ondřej Surý
Assignee
Assign to
Time tracking