Re: [PATCH 4/7] fuse: add POSIX file locking support

[Miklos Szeredi]

> > +/*
> > + * It would be nice to scramble the ID space, so that the value of the
> > + * files_struct pointer is not exposed to userspace.  Symmetric crypto
> > + * functions are overkill, since the inverse function doesn't need to
> > + * be implemented (though it does have to exist).  Is there something
> > + * simpler?
> > + */
> > +static inline u64 fuse_lock_owner_id(fl_owner_t id)
> > +{
> > +	return (unsigned long) id;
> > +}
> 
> Add a constant, not-known-to-userspace offset to all ids?

I thought of that, but it seemd cryptographically not quite strong
enough.  But maybe it's better than nothing.

Thanks,
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/