Tim Jones <[EMAIL PROTECTED]> wrote: > That sounds like a very solid feature request.
I submitted this text: ***************** snip have you ever thought about plugin security? I mean methods to prevent that a plugin is replaced by another one? the RB runtime could at least: load only the plugins which match by name and not just load all plugins in the frameworks folder. This allows very easy code injection! and check the plugins by name, size and a checksum to make sure the correct plugin is there. For RB 2008r1 you can replace any plugin in the Frameworks folder with a new one. At some point in RB the plugins are loaded. So the runtime could call a function to load a plugin and pass: name and size. This would make sure that not all dylibs are loaded and code injection is much more difficult. Also it would make it a little bit harder to replace the plugin files. A checksum like SHA1 or simple CRC32 is also welcome. ***************** snip If you like the idea, I can place another one. Gruß Christian -- Over 1000 classes with 20000 functions in one REALbasic plug-in. The Monkeybread Software Realbasic Plugin v8.2. <http://www.monkeybreadsoftware.de/realbasic/plugins.shtml> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
