On Monday 18 April 2005 05:38 am, Christian Magnusson wrote: > That seems to be a good idea to expand the number of platforms > to support. It should be pretty easy to implement if using unfs3 > so it's just to dig into the code and spend some late nights > with coffee in front of the computer.. :) > > /Christian >
Exactly right. I've added the code to the CVS, in owfs/modules/ownfsd and made the structure look like the other projects. I got rid of the "Config" subdir which seems to be only for "exports" parsing -- something we won't need to do. My first thought is to do NO access control, rather add that to owlib in a more generic manner. The same constraints on access to ownfsd probably apply to owhttpd and owserver. We could employ anything from IP address restrictions to more elaborate controls. All of these protocols should be "tunnelable" with stunnel or ssh. Paul ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
