Skip to content

bind: named does not follow the system-wide crypto policy #356

Description

@NavidSassan

Bug description

The named.conf shipped by bind on the Red Hat family includes /etc/crypto-policies/back-ends/bind.config inside its options block, which applies the system-wide crypto policy to named. The role's template drops that include, so named ignores update-crypto-policies and the crypto_policy role.

Steps to reproduce

  1. Deploy the role.
  2. Run grep crypto-policies /etc/named.conf: no match, while the packaged /etc/named.conf contains the include.

Expected behavior

The include is kept, as in the packaged file.

Environment

LFOps main, Rocky Linux 9.8 and 10.2.

Additional context

The template also omits secroots-file, recursing-file and geoip-directory from the packaged file.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions