Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Prevent manual invocation of COM EXE?
Message
From
24/10/2012 17:28:35
 
 
To
23/10/2012 13:52:47
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Miscellaneous
Thread ID:
01555563
Message ID:
01555736
Views:
43
>>My first thought is to pass in a parameter with the CREATEOBJECT( ) call that invokes the COM EXE. If it doesn't get a parameter (or the right value of the parameter), it closes itself - maybe after popping up an explanatory message.
>
>We have some of that for our robot. If it doesn't receive a parameter, it closes by itself. But, this was to allow various robot definitions to be allocated to specific servers. However, it would then be an additional level of protection as it forces the user to create a desktop icon and pass a parameter that he would need to know.

That's an interesting use case, thanks. I agree that requiring a parameter with the correct value to be passed, offers a modest amount of security.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Previous
Reply
Map
View

Click here to load this message in the networking platform