Re: [securenfs-devel] What's next?

[David W. <wo...@pl...>]

> I think it makes sense to attack the mount, PAM, and server sections 
> first, before getting into the actual filesystem stuff so, 

Quick question, what are we going to call the client?  'mount.snfs'?

The server, I'm assuming will be called snfsd?

> Next few things to do:
>    - "shell" out classes and methods for the server
>    - "shell" out pam module (in accordance with PAM interface)
>    - "shell" out mount code - I am envisioning this as simply a 
> userlevel interface to the pam module that will handle per-user mount 
> requests as we discussed etc
>   - Test cases - put together a test case including a server that 
> manages tokens, and a client (for now at the user-level) that imitates 
> filesystem requests.  We can use this to get statistics on load, 
> timings, etc, as well as provide the framework for the statistics 
> portion of the server.

Sounds good.

I think we should also revisit the data structure for holding tokens,
IPs, and etc... on the server side.


> 
> How would you all like to proceed?  Should we meet again to do some of 
> this? or is it well enough understood/discussed to allow for splitting 
> it up and tackling it via email/individually?


I think that we should probably write a test of our threading model
first.  If there is a problem with that design, then we may need to
modify things.

As far as shelling out the code, I suggest that we get together to
do this.  Each thing is interconnected so it would be difficult to
assign jobs, unless someone wants to come up with a design for all
three!  :)

Dave


-- 
----------------------------------------------------------------
I encourage correspondence using GnuPG/OpenPGP encryption.
My public key:  http://www.cs.plu.edu/~dwolff/pgpkey.txt