server.allow-insecure aka rpc-auth-allow-insecure option does not work

Status: CLOSED NOTABUG   Aliases: None   Component: glusterd (Show other bugs) Hardware: Unspecified Unspecified   Priority unspecified Severity unspecified Target Milestone: --- Target Release: --- Assigned To: krishnan parthasarathi Docs Contact:   Whiteboard:   Keywords:     Blocks:   Show dependency tree / graph		Reported: 2013-06-27 22:08 EDT by Louis Zuckerman Modified: 2013-06-27 23:04 EDT (History) CC List: 1 user (show)   Fixed In Version:   Doc Text: Environment: Regression: --- Documentation: --- Verified Versions:

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

Groups:    None ( edit)

Description Louis Zuckerman  2013-06-27 22:08:20 EDT Description of problem: I need to allow clients to connect to the volume from insecure (unprivileged) ports >1024. There appears to be an option in 3.4 to do this: server.allow-insecure. However when I set this to "ON" or "on" it has no effect, glusterd still refuses to serve clients on unprivileged ports. Version-Release number of selected component (if applicable): 3.4.0beta3 I'll update this bug with steps to reproduce as soon as I have a good procedure for you. Thanks! Comment 1 Louis Zuckerman  2013-06-27 22:30:34 EDT Shortly after I filed this bug Vijay chatted me on IRC to let me know that in addition to setting server.allow-insecure to on, I also needed to manually add an option to glusterd.vol: option rpc-auth-allow-insecure on I restarted glusterd with the updated volfile and now I can use insecure ports. Thanks again! Comment 2 Louis Zuckerman  2013-06-27 22:51:33 EDT Ok now I have a real bug to report.... After making the change above to glusterd.vol my insecure client program is able to communicate with glusterd to fetch the volfile, however.... When I try to create a file in the volume, nothing happens -- no error, no crash, no file created. Then when I try to write data into that file, the process crashes and I get a core dump. To reproduce this problem see the instructions in the readme.md file of the libgfapi-jni project: https://github.com/semiosis/libgfapi-jni Those instructions include a "sudo bash" command which will run the test as root. But DO NOT run it as root to reproduce this problem. The test succeeds when run as root, but fails when run as an unprivileged user. Comment 3 Louis Zuckerman  2013-06-27 23:00:36 EDT Ok I feel dumb. The insecure client couldn't create or write to the file because the volume permissions didn't allow it. Once i did a chmod ugo+rwx on the volume, it worked. PEBKAC