On 11/10/04 3:53 PM, "Frank Engel" <[EMAIL PROTECTED]> wrote:
> Okay, now I am experimenting with accessing the Mac OS X Keychain from > an External in Rev. It seems to be working fine, except for one slight > problem: > > My standalone and the stack running under Rev are recognized by the > Keychain Services as being the same app! > > If I understand this correctly, this means that *ANY* Rev stack (at > least, any Rev stack built with that version of Rev) will be able to > access the same keychain data that my stack would on the same machine. > Needless to say this is quite insecure. I suspect it might have > something to do with the fact that the Rev engine is used in both cases > as the basic "application" part of the program. > > Does anyone have any experience with this, or know how to work around > this problem? It might take an enhancement request to get this fixed, > not sure... I think it may have to do with the fact that the underlying engine name is "Revolution" in both cases. However you can rename that; you just need to be careful. See my tip at: http://www.sonsothunder.com/devres/revolution/revolution.htm?_proc005 And look at the "Carbon Application (Mach-O)" part of it. You can change the name of the engine (just like you'd change the name of any file), but you need to make sure the Info.plist is updated as well. HTH, Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
