Description of problem:

/etc/pam.d/bindconf used to be a symbolic link to
/etc/pam.d/system-config-bind and similarly with
/etc/security/console.apps/bindconf.  With the current update
those symlinks were replaced by separate files.  True, a default
content remain the same as for the corresponding
"system-config-bind" but after some configuration changes this
may be not the case and effects may turn out to be surprising.
A deliberate decision of a side-effect of a build system?
If the first then why two in each location and potentially different
configuration files are needed?

Version-Release number of selected component (if applicable):
system-config-bind-4.0.0-1