Bug 895831

Summary: auth.allow limited to 1024 chars in 3.2.5 and perhaps later versions, can you increase to something much bigger or allow unlimited length or see bug 861932
Product: [Community] GlusterFS Reporter: csb sysadmin <admin>
Component: rpcAssignee: bugs <bugs>
Status: CLOSED DEFERRED QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 3.2.5CC: bugs, gluster-bugs, rhs-bugs, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-14 19:40:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description csb sysadmin 2013-01-16 05:23:43 UTC
Description of problem:

auth.allow seems to be limited to 1024 chars, at least in 3.2.5

Version-Release number of selected component (if applicable):

glusterfs 3.2.5, perhaps in later versions as well

How reproducible:

at least always in 3.2.5

Steps to Reproduce:
1. Create an auth.allow entry with enough IP addresses to exceed 1024 chars
2. auth.allow is truncated and anything past 1024 chars is not read/enforced or given access
  
Actual results:

auth.allow is truncated and anything past 1024 chars is not read/enforced or given access

Expected results:

auth.allow should not be truncated or should be dynamically allocated (unlimited length)

Additional info:

If you can add the ability for auth.allow to read hostname wildcards, a superset of the feature requested in bug 861932 comment 2 then that would help greatly too. I could easily reduce my auth.allow list to only a few hostname wildcards and get rid of most of the ip's and ip wildcards.

Comment 2 Niels de Vos 2014-11-27 14:54:54 UTC
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.