Bug 1044352 - [RFE] Exempting a list of client IPs or the RHS servers themselves from anonymous uid and gid feature and/or from root squashing
Summary: [RFE] Exempting a list of client IPs or the RHS servers themselves from anony...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: rpc
Version: mainline
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard: rpc-3.4.0?
Depends On:
Blocks: 1044387
TreeView+ depends on / blocked
 
Reported: 2013-12-18 07:44 UTC by Vikhyat Umrao
Modified: 2018-11-19 05:52 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1044387 (view as bug list)
Environment:
Last Closed: 2018-11-19 05:20:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 553 0 None None None 2018-11-19 05:52:00 UTC

Description Vikhyat Umrao 2013-12-18 07:44:08 UTC
Hi,

We do not have any feature in glusterFS to exempt some client IPs or the RHS servers from anonymous uid and gid feature and/or from root squashing.
This feature already exist in NFS /etc/exports.

NFS feature in /etc/exports example:
Example:

# sample /etc/exports file
/         master(rw) trusty(rw,no_root_squash)

This exports the entire filesystem to machines master and trusty.  In addition to write access, all uid squashing is turned off  for host  trusty.

/home/joe pc001(rw,all_squash,anonuid=150,anongid=100)

This example only use anonuid=150 and anongid=100 for host pc001.

We can come up with exempt host names list in RHS server.

Comment 3 Niels de Vos 2014-11-27 14:45:19 UTC
Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.

Comment 4 Vijay Bellur 2018-11-19 05:52:01 UTC
Migrated to github:

https://github.com/gluster/glusterfs/issues/553

Please follow the github issue for further updates on this bug.


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