Re: [Flightgear-devel] Nasal security / fg_scenery

[Rebecca N. P. <reb...@zo...>]

> and it's a bit ugly to add all my _scenery_ paths to --fg-aircraft=

That's the problem that
> On 30/07/15 23:12 (
> http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/55B9CA69.6060201%40zoho.com/#msg34331214
> ), Rebecca N. Palmer wrote:
>> An alternative solution [to allow 3rd party scenery to use Nasal
>> without making /sim/terrasync/scenery-dir a can-read-anything security
>> hole] would be to internally have two variables: the current
>> fg_scenery (includes terrasync dir) and a new secure_fg_scenery
>> (explicitly-set fg-scenery only), and allow the latter.  Ugly, but
>> unlike the "throw out /sim/terrasync/scenery-dir" option, at least not
>> end-user-facing ugly.
> I'm thinking of trying this as well; comments?

was referring to, and has now been fixed (requires flightgear+fgdata 
update): explicitly-set scenery directories (but not the Terrasync 
directory, as Nasal can change that) are now allowed.