Bug 1321921 - auth.allow option with negation ! (!192.168.*.*) should not allow !192.168.*.* address
Summary: auth.allow option with negation ! (!192.168.*.*) should not allow !192.168.*...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1321916
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-29 11:39 UTC by Gaurav Kumar Garg
Modified: 2019-05-09 10:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-09 10:10:32 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Gaurav Kumar Garg 2016-03-29 11:39:04 UTC 
Description of problem:

Currently, when user set auth.allow option with negation ! (!192.168.*.*) then while mounting volume on !192.168.*.* ip-address Gluster is allowing mounting of volume. It should reject mounting that volume.



Steps to Reproduce:
1. somehow set auth.allow opting with negation ip-address/hostname and try to mount that volume from that ip-address/hostname.


Actual results:
 it will allow mounting the volume. 

Expected results:
because of negation in auth.allow it should allowing mounting of that volume.
Comment 1 SATHEESARAN 2016-03-30 01:58:50 UTC 
Gaurav,

Is this a new feature request or auth.allow already allows using negation ?
Comment 2 SATHEESARAN 2016-03-30 02:00:57 UTC 
(In reply to SATHEESARAN from comment #1)
> Gaurav,
> 
> Is this a new feature request or auth.allow already allows using negation ?

Just now found out the RFE bug[1]

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1321916
Comment 5 Amar Tumballi 2019-05-09 10:10:32 UTC 
We are not picking this issue in upcoming releases, and hence marking as DEFERRED. Will revisit after couple of releases depending on time/resource.
Note You need to log in before you can comment on or make changes to this bug.