Bug 707590 - Authconfig should warn of incorrect URI syntax for literal IPv6 addresses
Summary: Authconfig should warn of incorrect URI syntax for literal IPv6 addresses
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: authconfig
Version: 6.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: David Spurek
URL:
Whiteboard:
Depends On:
Blocks: 947781
TreeView+ depends on / blocked
 
Reported: 2011-05-25 13:20 UTC by Stephen Gallagher
Modified: 2015-03-02 05:26 UTC (History)
8 users (show)

Fixed In Version: authconfig-6.1.12-16.el6
Doc Type: Enhancement
Doc Text:
No docs needed
Clone Of:
Environment:
Last Closed: 2014-10-14 07:44:17 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1558 0 normal SHIPPED_LIVE authconfig bug fix and enhancement update 2014-10-14 01:27:53 UTC

Description Stephen Gallagher 2011-05-25 13:20:10 UTC
Description of problem:
http://www.ietf.org/rfc/rfc2732.txt requires that URIs containing a literal IPv6 address must have the address wrapped in brackets in order to differentiate the end of the address from the optionally-specified port.

Right now, it is possible to specify:
ldap://fc00::126:25
in authconfig without error or warning. This URI will be unusable for either nss_ldap or SSSD (as it will fail to parse).

Authconfig should validate that a URI is valid under RFC 2732. Probably the best way to accomplish this would be to pass the provider LDAP URIs into the python urlparse library for validation.

It should not be permissible to save a configuration for which urlparse returns an error.

Version-Release number of selected component (if applicable):
authconfig-6.1.12-5.el6

Comment 2 RHEL Program Management 2011-07-06 01:31:48 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 unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 RHEL Program Management 2012-05-03 05:14:04 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2013-10-14 01:05:19 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.

Comment 14 errata-xmlrpc 2014-10-14 07:44:17 UTC
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/RHBA-2014-1558.html


Note You need to log in before you can comment on or make changes to this bug.