Bug 765359 (GLUSTER-3627)
Summary: | Local user's can abuse gluster | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | David <db.pub.mail+gluster> |
Component: | glusterd | Assignee: | Kaushal <kaushal> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 3.2.3 | CC: | aavati, amarts, gluster-bugs, jdarcy, kdhananj, kparthas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-20 06:07:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David
2011-09-25 07:03:39 UTC
Its a good idea to remove the feature of giving a 'filename' for the log filename option (which is changed already in master), instead only allow directories in which we can create the log files. Actually, that's not the issue here. Perhaps I wasn't clear enough. The title of the bug is "Local user's can abuse gluster" and I gave an example of abusing one of the many gluster CLI commands (as the nobody user). The actual issue here is that "Local user's can abuse gluster" (non-root users) ... and they really shouldn't be able to abuse it :p Remember _any_ local user can delete _any_ gluster volume available (from what I can tell) (and create a new one). That can be solved by having an option in 'glusterd.vol', 'option rpc-auth-allow-insecure off'. That way, glusterd doesn't allow any connection from user programs. Please check if that is enough. (In reply to comment #3) > That can be solved by having an option in 'glusterd.vol', 'option > rpc-auth-allow-insecure off'. That way, glusterd doesn't allow any connection > from user programs. Please check if that is enough. It seem to fix the (patched) cli access from the nobody user. Why isn't that setting 'off' by default? In the current releases, the default setting for glusterd is rpc-auth-allow-insecure off. So this shouldn't be an issue anymore. |