Bug 764874 (GLUSTER-3142) - Introduce bind-insecure option for glusterd
Summary: Introduce bind-insecure option for glusterd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3142
Product: GlusterFS
Classification: Community
Component: transport
Version: mainline
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-07 07:53 UTC by shishir gowda
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description shishir gowda 2011-07-07 07:53:21 UTC 
For glusterd to scale, it should be able to bind not just to secure (<1024).

This will be a xlator-option, and for a glusterd to accept insecure connections, rpc-auth-allow-insecure option should be set to on
Comment 1 Anand Avati 2011-07-24 15:45:15 UTC 
CHANGE: http://review.gluster.com/11 (This is required if the number of connections from the glusterd) merged in master by Anand Avati (avati)
Note You need to log in before you can comment on or make changes to this bug.