Bug 811987 - autofs: maximum key name must be PATH_MAX
Summary: autofs: maximum key name must be PATH_MAX
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-12 13:13 UTC by Dmitri Pal
Modified: 2020-05-02 16:51 UTC (History)
3 users (show)

Fixed In Version: sssd-1.9.1-1.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2013-02-21 09:23:19 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2342 0 None None None 2020-05-02 16:51:35 UTC
Red Hat Product Errata RHSA-2013:0508 0 normal SHIPPED_LIVE Low: sssd security, bug fix and enhancement update 2013-02-20 21:30:10 UTC

Description Dmitri Pal 2012-04-12 13:13:49 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1300

When I limited the maximum key length to {{{NAME_MAX}}} I forgot about direct keys. Ian Kent reminded me in https://bugzilla.redhat.com/show_bug.cgi?id=683523#c80 that direct keys can be full paths.

Comment 1 RHEL Program Management 2012-07-10 07:06:32 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 2 RHEL Program Management 2012-07-11 02:05:31 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 4 Kaushik Banerjee 2012-11-28 10:33:54 UTC
Verified with version 1.9.2-21.

Verifed using the tool autofs_test_client
# echo /largepathfolder1/largepathfolder2/largepathfolder3/largepathfolder4/largepathfolder5/largepathfolder6/largepathfolder7/largepathfolder8/largepathfolder9/largepathfolder10/largepathfolder11/largepathfolder12/largepathfolder13/largepathfolder14/largepathfolder15 | wc -c
262

# ./autofs_test_client -n /largepathfolder1/largepathfolder2/largepathfolder3/largepathfolder4/largepathfolder5/largepathfolder6/largepathfolder7/largepathfolder8/largepathfolder9/largepathfolder10/largepathfolder11/largepathfolder12/largepathfolder13/largepathfolder14/largepathfolder15 auto.direct
setautomntent done for auto.direct
key: /largepathfolder1/largepathfolder2/largepathfolder3/largepathfolder4/largepathfolder5/largepathfolder6/largepathfolder7/largepathfolder8/largepathfolder9/largepathfolder10/largepathfolder11/largepathfolder12/largepathfolder13/largepathfolder14/largepathfolder15		value: -fstype=nfs,rw kau63.kautest.com:/export/largepathfolder
endautomntent done for auto.direct


The tool autofs_test_client was built as per the steps given by Jakub:

1. grab the SRPM from brew

2. install all the build dependencies:
    yum-builddep sssd-1.9.2-21.el6.src.rpm

3. install the SRPM
    rpm -i sssd-1.9.2-21.el6.src.rpm

4. compile the SSSD
    rpmbuild -bc ~/rpmbuild/SPECS/sssd.spec

5. go to the build directory
    cd ~/rpmbuild/BUILD/sssd-1.9.2/

6. build the tests
    make tests

You should see a binary called autofs_test_client now. The binary talks
the same protocol as the autofs itself, so you can use it to retrieve
all keys from a particular map:
     ./autofs_test_client auto.master

Or just one key from a map:
     ./autofs_test_client -n somelongkey auto.master

Comment 5 errata-xmlrpc 2013-02-21 09:23:19 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/RHSA-2013-0508.html


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