On Windows, you make something executable by putting .exe at the end. Of course, if it's not a real executable, nothing will happen, and if it is a real executable, and you don't put .exe at the end, it won't execute. This actually makes it a simple matter to send someone what looks like a jpg file, but with .exe at the end, and because Windows is hiding known extensions by default, (I know you can change that) you can trick a user into double clicking it and executing malicious code. Not so simple for a unix/linux based system. If the executable bit is in the file itself, Rev for Windows should be able to set it, but if it's some hidden system file somewhere, like an acl, then there is no real way to do it methinks.
Bob On May 19, 2010, at 1:59 PM, J. Landman Gay wrote: > Mark Swindell wrote: >> Quite the conundrum. Thanks for the explanation. New motto: Write >> once, wrestle lots, and deploy on multiple platforms. > > To be fair, it's easy and as advertised to build on all platforms from any > OS, with this one exception of building for OS X from Windows. You can't > really blame Rev for not being able to support something that Windows isn't > capable of doing. Windows is completely unaware of any unix-based > permissions. Going the other direction -- building on other platforms for > Windows deployment -- works fine and as expected. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
