Bug 764600 (GLUSTER-2868) - Add xlator-option to support insecure-bind for clients
Summary: Add xlator-option to support insecure-bind for clients
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2868
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-02 09:12 UTC by shishir gowda
Modified: 2014-04-09 20:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description shishir gowda 2011-05-02 09:12:46 UTC 
glusterfs clients bind to only secure ports (<1024).
Add xlator option to support clients to bind to any available port.
server.allow-insecure should be turned on to make it work.
Comment 1 Anand Avati 2011-05-04 09:00:15 UTC 
PATCH: http://patches.gluster.com/patch/7111 in master (gf_auth also needs to handle server.allow-insecure)
Comment 2 Anand Avati 2011-05-12 13:29:19 UTC 
PATCH: http://patches.gluster.com/patch/7112 in master (Introduce client-allow-insecure xlator-option.)
Comment 3 Anand Avati 2011-05-31 13:10:50 UTC 
PATCH: http://patches.gluster.com/patch/7335 in master (client_bind: When allow-insecure xlator option is set, donot bind.)
Comment 4 Anand Avati 2011-05-31 13:11:56 UTC 
PATCH: http://patches.gluster.com/patch/7339 in release-3.1 (gf_auth also needs to handle server.allow-insecure)
Comment 5 Anand Avati 2011-05-31 13:12:01 UTC 
PATCH: http://patches.gluster.com/patch/7340 in release-3.1 (Introduce client-allow-insecure xlator-option.)
Comment 6 Anand Avati 2011-05-31 13:13:11 UTC 
PATCH: http://patches.gluster.com/patch/7308 in release-3.2 (gf_auth also needs to handle server.allow-insecure)
Comment 7 Anand Avati 2011-05-31 13:13:16 UTC 
PATCH: http://patches.gluster.com/patch/7336 in release-3.2 (Introduce client-allow-insecure xlator-option.)
Comment 8 Rahul C S 2011-06-09 08:50:14 UTC 
Mounted 1000 clients after enabling server.allow-insecure on option. Without the option, it fails to bind to a port >1024.
Comment 9 Louis Zuckerman 2014-04-09 20:26:43 UTC 
How do I use this?  Can you give a usage example please?
Note You need to log in before you can comment on or make changes to this bug.