Bug 1321921

Summary:	auth.allow option with negation ! (!192.168..) should not allow !192.168.. address
Product:	[Community] GlusterFS	Reporter:	Gaurav Kumar Garg <ggarg>
Component:	protocol	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	mainline	CC:	atumball, bugs, smohan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-09 10:10:32 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:
Bug Depends On:	1321916
Bug Blocks:

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.