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.
Description of problem:
It is possible to add invalid hostnames to netgroups with ipa netgroup-mod --addattr and --setaddr. This is being split out of bug 797256 into a separate bug here.
# ipa netgroup-add test1 --desc=asdf
----------------------
Added netgroup "test1"
----------------------
Netgroup name: test1
Description: asdf
NIS domain name: testrelm.com
IPA unique ID: 9a65ec84-7ccf-11e1-9e50-525400a8d770
# ipa netgroup-mod test1 --setattr=externalhost=anotherbadhost?
-------------------------
Modified netgroup "test1"
-------------------------
Netgroup name: test1
Description: asdf
NIS domain name: testrelm.com
External host: anotherbadhost?
# ipa netgroup-mod test1
--addattr=externalhost=anotherbadhost\!\@\#$\%\^\&\*\(\)
-------------------------
Modified netgroup "test1"
-------------------------
Netgroup name: test1
Description: asdf
NIS domain name: testrelm.com
External host: anotherbadhost?, anotherbadhost!@#$%^&*()
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. <setup IPA server>
2. ipa netgroup-add test1 --desc=asdf
3. ipa netgroup-mod test1 --setattr=externalhost=anotherbadhost?
4. ipa netgroup-mod test1
--addattr=externalhost=anotherbadhost\!\@\#$\%\^\&\*\(\)
Actual results:
External hosts with invalid characters in hostname are added to netgroup. See output in Description for examples.
Expected results:
Should there be some validation of valid characters for externalhost (and other attrs) from the addattr/setaddr options for the netgroup-mod command (and others)?
Additional info:
Verified.
Version ::
ipa-server-3.0.0-7.el6.x86_64
Manual Test Results ::
[root@rhel6-1 yum.local.d]# ipa netgroup-add test1 --desc=asdf
----------------------
Added netgroup "test1"
----------------------
Netgroup name: test1
Description: asdf
NIS domain name: testrelm2.com
IPA unique ID: 23f70f9c-2ab2-11e2-b742-525400239224
[root@rhel6-1 yum.local.d]# ipa netgroup-mod test1 --setattr=externalhost=anotherbadhost?
ipa: ERROR: invalid 'externalhost': only letters, numbers, _, and - are allowed. DNS label may not start or end with -
[root@rhel6-1 yum.local.d]# ipa netgroup-mod test1 --addattr=externalhost=anotherbadhost\!\@\#$\%\^\&\*\(\)
ipa: ERROR: invalid 'externalhost': only letters, numbers, _, and - are allowed. DNS label may not start or end with -
[root@rhel6-1 yum.local.d]# ipa netgroup-show test1
Netgroup name: test1
Description: asdf
NIS domain name: testrelm2.com
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0528.html