Re: question: permission checking for network filesystem

2001-05-24 Thread Jan Hudec
> > open mode has 4 bits: read, write, append and execute. > > I hope "write" and "append" interact nicely, giving 4 choices. > > 00 no write > 01 append only > 10 overwrite only (no file size change) > 11 full write, append, truncate, etc. ... that's 1) Wrong 2) I need 4 bits ... that's 16 cho

Re: question: permission checking for network filesystem

2001-05-22 Thread Jan Hudec
> You can write lookup so that it always succeeds and returns dummy inode > without sending anything and do all the work in open & inode operations. It'd be great if I could. But I can't. First, the inode data are checked by some vfs functions before driver is called (this being the bigest probl

Re: question: permission checking for network filesystem

2001-05-21 Thread Mikulas Patocka
> Agree, but it will improve behavior. Or speed, rather. Otherwise open would > take 3(!) roundtrips (instead of two - now lookup can't be get rid of) - > lookup, permission and open. The protocol can do all three in one request. > The problem is I can't tell the 3 calls from VFS belong together.

Re: question: permission checking for network filesystem

2001-05-21 Thread Jan Hudec
Hi, > > I'm trying to impelemnt a lightweight network filesystem and ran into > > trouble implementing lookup, permissions and open. > > > > The protocol requires me to specify open mode in it's open command. The > > open mode has 4 bits: read, write, append and execute. But I can't tell > > Th

Re: question: permission checking for network filesystem

2001-05-20 Thread David Wagner
Mikulas Patocka wrote: >If you are checking permissions on server, read/execute have no security >meaning. This seems a bit too strong. If I try to exec a file that has read permission enabled but not execute permission, I'd like this to fail. You can just imagine sysadmins who turn off exec bi

Re: question: permission checking for network filesystem

2001-05-20 Thread Mikulas Patocka
Hi > I'm trying to impelemnt a lightweight network filesystem and ran into > trouble implementing lookup, permissions and open. > > The protocol requires me to specify open mode in it's open command. The > open mode has 4 bits: read, write, append and execute. But I can't tell > execution from r

question: permission checking for network filesystem

2001-05-20 Thread Jan Hudec
Hi, I'm trying to impelemnt a lightweight network filesystem and ran into trouble implementing lookup, permissions and open. The protocol requires me to specify open mode in it's open command. The open mode has 4 bits: read, write, append and execute. But I can't tell execution from read in file