Project

General

Profile

Actions

Feature #4799

closed

Client Security for CephFS

Added by Mike Kelly about 11 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:

Description

As discussed on the #ceph IRC channel with gregaf and others, I would find some added level of client security in CephFS to be very useful.

I would like to be able to grant a given client key access to only a subtree (or subtrees) of the entire CephFS tree. I guess some pseudo-caps would look something like:

mon = "allow r" 
osd = "allow rw pool=guest01-data, allow r pool=common-data" 
mds = "allow rw tree=/guests/guest01, allow r tree=/guests/common" 

I think that, in order for these protections to be complete, you'd have to also have separate pools for each of these subtrees, otherwise I think someone could still enumerate all the objects in the default 'data' pool, and extract or manipulate other data. But, if it's possible to avoid that somehow, that would help make this easier to maintain with a large number of guests. Perhaps enforcing object prefixes for each of these trees would avoid the need for zillions of pools, and still allow restrictions at the OSD layer?

Actions #1

Updated by Greg Farnum almost 8 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF