20,741
edits
Frequently asked questions: Difference between revisions
Jump to navigation
Jump to search
→Content Protection
| Line 298: | Line 298: | ||
|added = May 9th, 2016 | |added = May 9th, 2016 | ||
|script_version = 0.37 | |script_version = 0.37 | ||
}}</ref> | |||
The thing to keep in mind is that no matter what your source format is (dll, encrypted+signed, binary, etc.), ultimately your model mesh and textures and logical structure are read into internal OSG class structures. Once that has process has completed so the model can be rendered on screen, a person could call the appropriate write*File() function to save out your model's subtree into any of the supported formats. The only thing that is needed is access to the FlightGear source code to insert the function call in a strategic location. Ultimately, you can't completely protect your content work if you don't also completely control the situation at the application source code level. And this is a classic copy protection hacking strategy, insert the magic in the code after the distribution format has been authenticated/loaded/decoded and then write it out in a 'decrypted' format. People do it all the time, even with proprietary code. The value of the target usually determines how hard they are willing to work to steal it.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35074534/ | |||
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared | |||
library, and what legislation issues would that ensue? </nowiki> | |||
|author = <nowiki> Curtis Olson </nowiki> | |||
|date = May 9th, 2016 | |||
|added = May 9th, 2016 | |||
|script_version = 0.38 | |||
}}</ref> | }}</ref> | ||