Quoting Seth Forshee (seth.fors...@canonical.com):
> On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote:
> > Quoting Seth Forshee (seth.fors...@canonical.com):
> > > Filesystem uids which don't map into a user namespace may result
> > > in inode->i_uid being INVALID_UID. A symlink and
On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote:
> Quoting Seth Forshee (seth.fors...@canonical.com):
> > Filesystem uids which don't map into a user namespace may result
> > in inode->i_uid being INVALID_UID. A symlink and its parent
> > could have different owners in the filesystem
Quoting Seth Forshee (seth.fors...@canonical.com):
> Filesystem uids which don't map into a user namespace may result
> in inode->i_uid being INVALID_UID. A symlink and its parent
> could have different owners in the filesystem can both get
> mapped to INVALID_UID, which may result in following a
Quoting Seth Forshee (seth.fors...@canonical.com):
Filesystem uids which don't map into a user namespace may result
in inode-i_uid being INVALID_UID. A symlink and its parent
could have different owners in the filesystem can both get
mapped to INVALID_UID, which may result in following a
On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote:
Quoting Seth Forshee (seth.fors...@canonical.com):
Filesystem uids which don't map into a user namespace may result
in inode-i_uid being INVALID_UID. A symlink and its parent
could have different owners in the filesystem can both
Quoting Seth Forshee (seth.fors...@canonical.com):
On Fri, Sep 05, 2014 at 05:05:09PM +, Serge Hallyn wrote:
Quoting Seth Forshee (seth.fors...@canonical.com):
Filesystem uids which don't map into a user namespace may result
in inode-i_uid being INVALID_UID. A symlink and its parent
Filesystem uids which don't map into a user namespace may result
in inode->i_uid being INVALID_UID. A symlink and its parent
could have different owners in the filesystem can both get
mapped to INVALID_UID, which may result in following a symlink
when this would not have otherwise been permitted.
Filesystem uids which don't map into a user namespace may result
in inode-i_uid being INVALID_UID. A symlink and its parent
could have different owners in the filesystem can both get
mapped to INVALID_UID, which may result in following a symlink
when this would not have otherwise been permitted.
8 matches
Mail list logo