[securenfs-devel] What's next?

[Nathan Y. <na...@yo...>]

Okay, so we have example config files that I believe work for us, at 
least insofar as to further the design of the project... anyway, that 
brings us to:

I think it makes sense to attack the mount, PAM, and server sections 
first, before getting into the actual filesystem stuff so, the way I see 
it (throw in other ideas/comments as you see fit of course):

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.

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?

Nate