--- Melchior FRANZ wrote:
> Nasal (in SimGear) already had support for file I/O since the
> last Nasal update, but the line that would have activated it was
> commented out until yesterday. The now available Nasal "io"
> module allows some interesting stuff, such as direct appending
> of OBJECT entries to *.stg files from nasal code. But it's also
> potentially dangerous. What do we have to do to limit unwanted
> side effects, or rather: intentional malicious use of it?
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.
That way
- Aircraft would have access to "safe" I/O methods only
- Any new IO function would have to be added to a single .nas file and
could be easily scrutinized.
- Installing a simple tarballed aircraft from outside CVS is less risky,
as the aircraft .nas files has a limited number of IO functions available.
Is this something that can sensibly be done within the parser?
-Stuart
___________________________________________________________
What kind of emailer are you? Find out today - get a free analysis of your
email personality. Take the quiz at the Yahoo! Mail Championship.
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk
-------------------------------------------------------------------------
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
