the file writing security was adjusted back in 2017.3.1 to avoid CVE-2017-13709...
Re: [Flightgear-devel] custom logging output file / fix for CVE-2017-13709CVE-2017-13709 Detaili think you can tell FG that certain directories are allowed to be written to but i'm unable to easily find this information in the wiki and my google-fu seems to be off this morning
when i attempt the same as you describe, i see the following logged in the console and in the fgfs.log file...
- Code: Select all
55.96 [ALRT]:general The FGLogger logging system, via the '/logging/log/filename' property, was asked to write to 'fg_log.csv', however this path is not authorized for writing anymore for security reasons. Please choose another location, for instance in the $FG_HOME/Export folder (/home/myuser/.fgfs/Export).
the segmentation fault happens afterward when a shutdown appears to be automatically triggered... i have backtraces for the crashing scenario and will forward them to the mailing list for analysis and remediation...
[Flightgear-devel] SIGSEGV when attempting to use F10->Debug->Logging with unwritable output pathif i specify a proper and writable path to the output file as given in the error output (/home/myuser/.fgfs/Export/fg_log.csv), there is no problem, no crash, and a proper csv file is written in the specified directory... i did try using "$FG_HOME/Export/fg_log.csv" but the $FG_HOME macro is not expanded and the defect is triggered as well...
for now, the easiest thing to do is to specify a proper path that FG can write the desired output file to...
thanks for the report!
[edited to add link to the dev mailing list thread]
[edited to add link to CVE-2017-13709 Detail]
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."