Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
I've locked the system further down. If people desire, then we can disable any file access by default. At the moment writing should only be possible with pattern ~/.fgfs/Export/* and ~/.fgfs/Scenery/*.stg. m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
* Melchior FRANZ -- Monday 16 June 2008: I've locked the system further down. var read_rules = [ [root ~ /*, 1], [home ~ /*, 1], ]; var write_rules = [ [home ~ /Scenery/*.stg, 1], [home ~ /Export/*, 1], ]; The 1 means ALLOW, whereas 0 would mean DENY. You probably know that from other configuration files. That way you can say, for example: [root ~ /*.nas, 0], [root ~ /*, 1], to allow all files under $FG_ROOT, except *.nas files. (That's assuming that there aren't any bugs in string.match and string.fixpath, etc. ;-) m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bug in Livery handling
Hi, Ups- I didn't want to send it to devel-list, but it seems the list is working again, so no problem! ;-) For those who aren't fit in german: I noticed that the livery handling over mp isn't working as expected. I can't see any change in livery or over home network. I know that bo105/plib are only correctly shown in fg/plib, and bo105/osg only in fg/osg. I didn't bother to make livery changing backwards compatible, but the skeleton isn't nice. I'll add some code to fix that. In the moment I can't prove it, because it seems that there is no out using the bo105/osg. And I'm against backward compatibly too. But in your local network you are probably using the same binaries for both machines, and I have no explanation for why the bo wouldn't show up correctly then. Right! In the property browser I can see, that the file-string is correctly sended, but it seems that the nasal code can't handle this. Also, I have no clue what the garbage in the terminal comes from. I've never seen that (or at least not in the last years). Yeah- this is really strange, and I think that this is cause of the bug. Regards HHS still in work: http://www.hoerbird.net/galerie.html But already done: http://www.hoerbird.net/reisen.html --- Melchior FRANZ [EMAIL PROTECTED] schrieb am Mo, 16.6.2008: Von: Melchior FRANZ [EMAIL PROTECTED] Betreff: Re: [Flightgear-devel] Bug in Livery handling An: flightgear-devel@lists.sourceforge.net Datum: Montag, 16. Juni 2008, 7:37 Hi, now that it went to the list, I'll also reply here. :-) * Heiko Schulz -- Monday 16 June 2008: www.hoerbird.net/liveryhandling_mp_bug.png I know that bo105/plib are only correctly shown in fg/plib, and bo105/osg only in fg/osg. I didn't bother to make livery changing backwards compatible, but the skeleton isn't nice. I'll add some code to fix that. But in your local network you are probably using the same binaries for both machines, and I have no explanation for why the bo wouldn't show up correctly then. Also, I have no clue what the garbage in the terminal comes from. I've never seen that (or at least not in the last years). m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
The rules are now read from $FG_ROOT/Nasal/IOrules or, if available, $FG_HOME/Nasal/IOrules. That way people who don't have write permission for $FG_HOME/Nasal/io.nas can still extend and modify the rules. The default is: READ ALLOW $FG_ROOT/* READ ALLOW $FG_HOME/* WRITE ALLOW $FG_HOME/Export/* This can be overridden with a file $FG_HOME/Nasal/IOrules that is either empty, or contains these rules: READ DENY * WRITE DENY * Should we use the more restrictive rules by default? Note, however, that file access via fgcommand() isn't affected by the rules at all. There's only an .xml extension enforced by, and it will abort if the file isn't a PropertyList. This should be safe enough. m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
Ehlo ppl ;) Can't you just restrict the io to the $FG_HOME dir or something? And if the user (I doubt that John Doe needs this...) requires permissions some where else then he/she could tell fgfs that with a cmd line argument? like --io-read=/myDir --io-read=/tmp --io-write=/etc/passwd ? /Sven Melchior FRANZ wrote: * Melchior FRANZ -- Monday 16 June 2008: people who don't have write permission for $FG_HOME/Nasal/io.nas err ... $FG_ROOT/Nasal/io.nas READ ALLOW $FG_ROOT/* [...] This can be overridden with a file $FG_HOME/Nasal/IOrules that is either empty, or contains these rules: READ DENY * WRITE DENY * err ... it can be overridden with any rules. The important point is that a local file doesn't add to the global rules, but replace them. And an empty file or one with READ DENY *\nWRITE DENY * is the most restrictive you can have. m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
* Sven Almgren -- Monday 16 June 2008: Can't you just restrict the io to the $FG_HOME dir or something? Sure: READ ALLOW $FG_HOME/* WRITE ALLOW $FG_HOME/* like --io-read=/myDir --io-read=/tmp --io-write=/etc/passwd ? Any of the options overwrites a previous one with the same name, so one would have to rewrite parts of options.cxx for that. (Yes, one can have several --config= options, but that's a different story.) You could, however, list all pattern in one option, separated by a (semi)colon. But then it would be harder to quickly add a path for a test or something. One could, of course, use this instead: --prop:io-read=/myDir --prop:io-read[1]=/tmp ... But that would use the property tree, and then a malign *-set.xml file could sneak in whatever it wants. Though ne could work around that. An option --io-read would imply that this is a generic mechanism for all file IO, which it isn't. It's for Nasal's io.open() *only*, and handled in Nasal to 100%. Given the bunch of libraries it would be rather difficult to apply the checks to every file IO. You'd really have to use LD_PRELOAD, which won't work on MS Windows. In other words: yes, it could (and maybe should) be done with options. And I'd even review and possibly apply a patch that implements it. At least for now we should be reasonably safe from evil people and have time to find better solutions. :-) m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
* Melchior FRANZ -- Monday 16 June 2008: At least for now we should be reasonably safe from evil people and have time to find better solutions. BTW: Why the sudden paranoia? Not that we should have waited much longer for some security enhancements in any case, but the fact that there seem now to be web sites with random fgfs addons to download made me feel a bit uncomfortable. It was all too easy to cause quite some damage, and not everyone reviews the fgfs stuff he installs. Of course, it would be better to keep the official repositories as the central place for all sorts of scenery and aircraft addons, and not to rely on any outside source. And to review the stuff before committing. :-) m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
Melchior FRANZ wrote: * Melchior FRANZ -- Monday 16 June 2008: At least for now we should be reasonably safe from evil people and have time to find better solutions. BTW: Why the sudden paranoia? Not that we should have waited much longer for some security enhancements in any case, but the fact that there seem now to be web sites with random fgfs addons to download made me feel a bit uncomfortable. It was all too easy to cause quite some damage, and not everyone reviews the fgfs stuff he installs. Of course, it would be better to keep the official repositories as the central place for all sorts of scenery and aircraft addons, and not to rely on any outside source. And to review the stuff before committing. :-) m. A little paranoia now and then can only be healthy ;) But as you said, you could use colons or commas for the list of files, like --prop:io-read=/myDir,/tmp,/dev/null or some other separator, like : or ;.Colon (:) is a bad idea as it would mess with windows paths that involves a drive:, you could use semi-colon (;) but that would require escaping on linux, if you don't do it like --prop:io-read=/myDir;/tmp;/dev/null;c:\windows\system32\sam. About the tree, you could use it like you saied, but that would be a hell to write, but I guess that would be a good solution otherwise... but parsing the line from above would also be doable, but I guess your tree names are more mainstream :P But can't you just restrict the io to a single directory and then let the users install their extensions there? or just export the entire FG_ROOT? But is this really needed? How does M$ flightsim extensions do? You have to trust the source somewhat, We could sneak in bad code in fgfs too, and ppl would run it anyway... Can the addoncreators be trustet as much as we can? Comments? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
On Mon, 16 Jun 2008 15:40:54 +0200, Sven wrote in message [EMAIL PROTECTED]: Melchior FRANZ wrote: * Melchior FRANZ -- Monday 16 June 2008: At least for now we should be reasonably safe from evil people and have time to find better solutions. BTW: Why the sudden paranoia? Not that we should have waited much longer for some security enhancements in any case, but the fact that there seem now to be web sites with random fgfs addons to download made me feel a bit uncomfortable. It was all too easy to cause quite some damage, and not everyone reviews the fgfs stuff he installs. Of course, it would be better to keep the official repositories as the central place for all sorts of scenery and aircraft addons, and not to rely on any outside source. And to review the stuff before committing. :-) m. A little paranoia now and then can only be healthy ;) But as you said, you could use colons or commas for the list of files, like --prop:io-read=/myDir,/tmp,/dev/null or some other separator, like : or ;.Colon (:) is a bad idea as it would mess with windows paths that involves a drive:, you could use semi-colon (;) but that would require escaping on linux, if you don't do it like --prop:io-read=/myDir;/tmp;/dev/null;c:\windows\system32\sam. ..it's also possible to do our own thing, e.g. :: (2 colons): --prop:io-read=/myDir::/tmp::/dev/null::c:\windows\system32\sam or say : (a : plus 2 's, unless it breaks something) like: --prop:io-read=/myDir:/tmp:/dev/null:c:\windows\system32\sam building our own separator from more than one character, or even use one or more utf-8, e.g. the Norwedian letter å (a-ring) is pronounced awe just like the Norwegian og which btw means and in English, e.g.: --prop:io-read=/myDir:å:/tmp:å:/dev/null:å:c:\windows\system32\sam, I'm not aware of anyone using å: as a Microsoft drive name. ;o) About the tree, you could use it like you saied, but that would be a hell to write, but I guess that would be a good solution otherwise... but parsing the line from above would also be doable, but I guess your tree names are more mainstream :P But can't you just restrict the io to a single directory and then let the users install their extensions there? or just export the entire FG_ROOT? But is this really needed? How does M$ flightsim extensions do? You have to trust the source somewhat, We could sneak in bad code in fgfs too, and ppl would run it anyway... Can the addoncreators be trustet as much as we can? Comments? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bug in Livery handling
* Melchior FRANZ -- Monday 16 June 2008: I know that bo105/plib are only correctly shown in fg/plib, and bo105/osg only in fg/osg. bo105/plib should now show up correctly in fg/osg (with random variant and special emblem). bo105/osg are not shown correctly in fg/plib, and probably never will. m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT] How can I start up in air?
On Fri, 2008-06-13 at 14:14 +0200, Holger Wirtz wrote: Hi, sorry, this is perhaps a little bit off topic but I haven't found any answers the last days: How can I start up at a specific position in air? I found some hints at http://wiki.flightgear.org/index.php/Starting_in_the_Air but if I use the SenecaII I have the problem that the magnetos are off, the nose of the plane is turned down to earth and the simulation is in running state. I tried the following: fgfs \ --altitude=5000 \ --heading=270 \ --vc=110 \ --vor=OAK \ --offset-distance=5 \ --offset-azimuth=270 \ --aircraft=SenecaII-jsbsim \ --prop:/controls/engines/engine/throttle=0.8 \ --prop:/controls/engines/engine/magneto=true \ --prop:/controls/engines/engine/magneto[0]=true \ --prop:/controls/engines/engine[0]/magneto=true \ --prop:/controls/engines/engine[1]/magneto=true \ --prop:/controls/engines/engine[0]/magneto[0]=true \ --prop:/controls/engines/engine[1]/magneto[0]=true \ --prop:/controls/engines/engine[0]/starter=true \ --prop:/controls/engines/engine[1]/starter=true \ --enable-freeze \ --geometry=170x100 I need this for learning landings and ILS approaches towards an airport. For this it would be nice when the simulations starts at a well trimmed point... Has anyone an idea how to get this running? Thanks, Holger It didn't help me, but perhaps it will lead you to the right path. /controls/engines/engine/magneto is the same property as /controls/engines/engine[0]/magneto and /controls/engines/engine[0]/magneto[0] That is, the subscript [0] is the same as no subscript. The command line property tree doesn't understand true and false use 1 and 0 instead. SenecaII uses three settings for each engine's magnetos: --prop:/controls/engines/engine[0]/magneto[0]=1 \ --prop:/controls/engines/engine[0]/magneto[1]=1 \ --prop:/controls/engines/engine[0]/magnetos=3 \ \ --prop:/controls/engines/engine[1]/magneto[0]=1 \ --prop:/controls/engines/engine[1]/magneto[1]=1 \ --prop:/controls/engines/engine[1]/magnetos=3 Good luck, Ron - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
Melchior FRANZ wrote: It's well known that Nasal has an io module with wrappers around fopen(), fclose(), etc. An aircraft that you install, or even scenery objects with embedded Nasal could in the past use this to delete the contents of your whole home directory, or to append commands to ~/.bashrc, and thus execute code next time you open a shell! I must admit I haven't follow the thread completely, but I think the number of occasions where one would allow FlightGear to write anything to the disk is so small that it might be better to handle those cases with internal functions. In other words; Scripts are allowed to read anything but can only write using predefined functions. (What are the reasons to write to a file anyway?) Erik - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
Melchior FRANZ wrote: * Sven Almgren -- Monday 16 June 2008: like --io-read=/myDir --io-read=/tmp --io-write=/etc/passwd ? One could, of course, use this instead: --prop:io-read=/myDir --prop:io-read[1]=/tmp ... I don't consider any command line option a security thread since writing to files can be done a lot easier than using FlightGear.. Any script that could write to the disk however is a security thread since not everybody (or probably no one) would check every file of a downloaded aircraft for security problems. Erik - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
It's funny that nobody cared a year long, and now that the danger is supposed to be banned, people get scared and nervous. :-} * Erik Hofman -- Monday 16 June 2008: (What are the reasons to write to a file anyway?) Writing non-PropertyList XML files, like they are used in the traffic manager and for flight plans. Writing *.stg files (adding models or adjusting elevations for the current terrain). m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
Sven Almgren wrote: But is this really needed? How does M$ flightsim extensions do? You have to trust the source somewhat, We could sneak in bad code in fgfs too, and ppl would run it anyway... Can the addoncreators be trustet as much as we can? Sure. FlightGear is a local program, and software it loads from the local drive can certainly do local I/O if it wants without breaking typical security models. That's the whole idea behind being able to download software from the internet in the first place. :) My historical fear has been the interaction with the MP environment: the MP code can write to the property tree, and arbitrary property nodes have on various occasions be hooked to execute Nasal code. Being able to execute arbitrary Nasal code on another machine over the network would be a security disaster if that code could do I/O or spawn programs, etc... What Melchior has done is fine with me, architecturally. Ideally, I guess I'd prefer a sandbox on the other side: an architecture that expressly prevents network data from being executed somehow, probably by strictly limiting the areas in the property tree it can write to. But this kind of architecture can work too: it just requires that every potentially unsafe operation be sandboxed in the same way as I/O. Andy - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
* Melchior FRANZ -- Monday 16 June 2008: Writing non-PropertyList XML files, like they are used in the traffic manager and for flight plans. Correction: not for flight plans -- these are PropertyLists. But for the other stuff like parking files etc. The power of a system isn't defined by what is used, but by what can be done, and allowing scripts to write to the disk is a powerful feature. Dangerous if uncontrolled. But at the moment write access should only be possible to $FG_HOME/Export/, so I don't really see the problem. And if we offer the feature, people will find innovative ways to use it. If we don't, they won't. While we are at it, we could strip off a lot of other features that not many people use. What about SP_FDM, jpeg factory, the bits.nas library, UIUC, LaRCSim, ... m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
Melchior FRANZ wrote: It's funny that nobody cared a year long, and now that the danger is supposed to be banned, people get scared and nervous. :-} I don't, I just though I could help here. Erik - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
Melchior FRANZ wrote: * Erik Hofman -- Monday 16 June 2008: (What are the reasons to write to a file anyway?) Writing non-PropertyList XML files, like they are used in the traffic manager and for flight plans. Maybe making sure the file ends with .xml could also help a lot. Erik - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
* Erik Hofman -- Monday 16 June 2008: Maybe making sure the file ends with .xml could also help a lot. io.nas:113: writexml() if(substr(path, -4) != .xml) path ~= .xml; fg_commands.cxx:1365: do_save_xml_from_proptree() if (file.extension() != xml) file.concat(.xml); Both added by me quite a while ago, if I may add. :-) m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted
* Melchior FRANZ -- Monday 16 June 2008: * Erik Hofman -- Monday 16 June 2008: (What are the reasons to write to a file anyway?) Writing non-PropertyList XML files, like they are used in the traffic manager and for flight plans. Writing *.stg files (adding models or adjusting elevations for the current terrain). Writing an *.svg file with a graphic showing the flight path, or flight parameters. Or a smilie. Writing or modifying a PostScript file, for example to hand out to children on LinuxTag or flight shows, with flight time and duration automatically filled in. You could move that straight to the printer. (Caution: an attacker could empty your toner cartridge with that! ;-) Writing a TeX file with a table showing flight parameters, fuel consumption, whatever. None of this crucial, and all of it doable with external scripts from XML exported data. But the possibility to do it with Nasal drivers from within is nice. And something that other flight sims might not be able to do. Maybe something that our corporate users would like to do. They'll probably not download questionable aircraft from 3rd party sources. :-) m. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-users] Where to get terragear?
On Mon, 2008-06-16 at 21:20 -0430, Ernesto Hernandez-Novich wrote: What happened to http://www.terragear.org? Where can I get the latest TerraGear? Terragear.org is still there for me... There has been a server problem that is mostly resolved at this point. Look at the page http://www.terragear.org/cvs.html The instructions are good with two exceptions: 1: The server doesn't like to be called cvs.terragear.org, call it cvs.flightgear.org instead. Checking out a copy of the source code The TerraGear source code is available via anonymous (read only) cvs. To check out a local copy of the TerraGear source, run the following commands: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/TerraGear-0.0 login CVS passwd: guest cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/TerraGear-0.0 co source 2: The Interactive CVS log browser is not functional yet. Also, the Terragear project has slightly forked, you might want to try this version instead: http://mapserver.flightgear.org/git/?p=terragear-cs;a=tree Good luck, Ron - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
