Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
The named initscript checks the existence of rndc.key file
on the server start-up.
Consequence:
User having a custom rndc configuration may include a key from a file located in other than the default place. In such situation the initsctipt generates a rndc.key in the default location even if it is not needed and used.
Fix:
The initscript was fixed to check for include statement with "rndc.key" in the rndc configuration before generating the rndc.key file.
Result:
As a result, if user has a custom rndc configuration including a rndc.key file from other than the default location, then the initscript will not generate a rndc.key file in the default location during the server start-up
Created attachment 598934[details]
Patch that should fix the described problem
Description of problem:
When starting or restarting bind, there is always a new key generetad in /etc/rndc.key. This is wrong because I have specified a path in /etc/rndc.conf. My key is located in /etc/named/rndc.key.
Version-Release number of selected component (if applicable):
9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6
How reproducible:
Always
Steps to Reproduce:
1. Use a config file for rndc, rndc.conf, that looks like this
# rndc.conf
include "/etc/named/rndc.key";
options {
default-key "rndc.key";
default-server 127.0.0.1;
default-port 953;
};
2. restart bind
Actual results:
a key is generated in /etc/rndc.key
Expected results:
no key in /etc/rndc.key
Additional info:
There are two problems here:
- depending on machine type, this can take a rather long time (using a virtual machine, it takes more than one minute)
- We have a third party tool which always tries to take the key in /etc/rndc.key if this key exists. It refuses to work, because, it takes the wrong key when a new one is generated...
I've attached a patch which could you give a better hint of what I mean.
Thanks!
Created attachment 732640[details]
Generate rndc.key only if there is NO custom rndc.conf with path
Basically if you need to have custom rndc.conf with path to rndc.key then you
should also generate the key by yourself.
The attached patch changes initscript behaviour so that now the rndc.key will
be generated in /etc only if there is no rndc.key AND there is no /etc/rndc.conf
with "include" line with the path to rndc.key.
Comment 6RHEL Program Management
2013-10-14 00:33:37 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Created attachment 598934 [details] Patch that should fix the described problem Description of problem: When starting or restarting bind, there is always a new key generetad in /etc/rndc.key. This is wrong because I have specified a path in /etc/rndc.conf. My key is located in /etc/named/rndc.key. Version-Release number of selected component (if applicable): 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6 How reproducible: Always Steps to Reproduce: 1. Use a config file for rndc, rndc.conf, that looks like this # rndc.conf include "/etc/named/rndc.key"; options { default-key "rndc.key"; default-server 127.0.0.1; default-port 953; }; 2. restart bind Actual results: a key is generated in /etc/rndc.key Expected results: no key in /etc/rndc.key Additional info: There are two problems here: - depending on machine type, this can take a rather long time (using a virtual machine, it takes more than one minute) - We have a third party tool which always tries to take the key in /etc/rndc.key if this key exists. It refuses to work, because, it takes the wrong key when a new one is generated... I've attached a patch which could you give a better hint of what I mean. Thanks!