Hi Mark, I often have thought about signing my program to avoid this "do you want to continue?" What kept me from doing this up to now, is that I don't know what happens with update setups, new versions of the same program, etc. Somebody told me, that I have to apply for a new certificate at Microsoft for every patch or new version, what I didn't really liked Do you know anything about this process? Thanks Tiemo
> > Due to the fact that there are so many bug^H^H^Haspects of Microsoft's > code that people can exploit^H^H^Hutilize, Microsoft created a way to > digitally sign your application when you release it. The code is > directly traceable back to you and verified by the installation code. > That way if somebody or some program messes with your application and > modifies it in any way the verification will fail and the user will be > presented with a warning message before installation proceeds. It's a > way of ensuring that the application is intact from the time it leaves > your hands to the time the end-user installs it. If you don't sign > your application then the user will be get a message to that effect > and "do they want to continue?". IT departments hate that and would > probably be more likely to let signed apps be installed. YMMV. > > -- > -Mark Wieder > mwie...@ahsoftware.net > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
