Re: what's next for the linux kernel?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Luke Kenneth Casson Leighton wrote:
 the bastion sftp example i gave which required selinux on top of a much
 broader set of POSIX file permissions demonstrates the fallacy of your
 statement.

 try to achieve the same effect with POSIX - even POSIX ACLs
 (uploader only has create and write, not read, not delete;
  downloader has read and delete, not write, not create)

 and you will fail, miserably, because under POSIX, write implies
 create.

you, however, seem to be missing the point that these are special circumstances. in 99% of all cases, regular unix file permissions are sufficient. when you start needing special silly permissions for things like this, we have special silly tools to accommodate you. Use them. Deal with it.

adding a permissions schema similar to that found in windows/netware would only unneccessarily complicate things, and most likely end up breaking everything.

bottom line: if you want to see support like this in linux, write a filesystem with these capabilities built-in. If you don't want to/can't write it, then stop complaining and continue to use netware (read: shit or get off the pot).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux