> * Stuart Buchanan -- Friday 30 March 2007: > > Functionally, it seems reasonable to force all IO access through a wrapper > > .nas file in $FG_ROOT/Nasal that could attempt to restrict dangerous > > activities. > > But every Nasal code would have to have access to use those > wrapper/validator functions ... and could then also overwrite them. > Or bypass the wrappers and use the wrapped core functions directly. > I assume any validation would have to be done in C++. > Would it be reasonable to add a RESTRICT_IO define within Nasal itself that stripped any path data from a filename and forced it to /tmp or some other default directory specified by a non-nasal Nasal configuration file?
g. -- "I'm not crazy, I'm plausibly off-nominal!" Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
