Project

General

Profile

Bug #10413

BIND plugins are not copied into chroot

Added by Scott Dial 2 months ago. Updated 2 months ago.

Status:
Feedback
Priority:
Normal
Category:
BIND
Target version:
-
Start date:
04/02/2020
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.5
Affected Architecture:
All

Description

BIND 9.13.5 introduced a new plugin system, and the filter-aaaa support was moved to a plugin, so we need to copy the plugins into the chroot to allow using this feature. Previously, "filter-aaaa-on-v4 yes;" was a built-in option to filter out AAAA records when queried via an IPv4 socket, but this filtering was out to a plugin. To perform the same functionality, you need to add a custom option to your views (since the filter plugins must be declared in views, if they are used):

plugin query "filter-aaaa.so" { filter-aaaa-on-v4 yes; };

Currently, this fails because the "filter-aaaa.so" file is not found. BIND expects there to be "named" directory in ${libdir} that contains plugins, which on our package computes out to "/usr/local/lib/named". However, the pfSense BIND package runs from the "/cf/named" chroot, so we need to copy those plugins into that chroot to allow their use.

History

#1 Updated by Jim Pingle 2 months ago

  • Status changed from New to Pull Request Review

#2 Updated by Renato Botelho 2 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

Also available in: Atom PDF