Making ActiveX safe..?

[kenjoswe]

Hi all,

I've tried to run an ActiveX on our intranet but when I do so I get the message:
"Some software (ActiveX controls) on this page might be unsafe..." this results that the control wont load from the html-page unless you lower the safty level.

I have tried the Deployment Wizard but this doesn't work.

How can I make the ActiveX safe so that I can run it with the default settings on the browser?

/Kent J.

 

[Ruairi]

To run active-x controls you have to have a lower safety setting. period. If you're on an intranet why would you need high safety settings anyway. The browser makes a ditinction between a local intranet and the internet. You should be able to lower the safety settings for the intranet zone and leave them high for internet zone. Ruairi

Could your manufacturing facility benefit from real time process monitoring? Would you like your employees to be able to see up to the minute goal and actual production?
For innovative, low cost solutions check out my website.

http://www.plccontroltechnologies.com

 

[GlennBSI]

kenjoswe,

When using ActiveX controls, there are two issues that you need to be aware of regarding security - whether or not they are signed and whether or not they are marked safe for scripting.

In IE5, even the low security setting will prompt the user if a control is unsigned or if it isn't marked safe for scripting, so you'll have to deal with that accordingly (either have the users change their settings or change it for them by pointing them to a .reg file that contains the security settings you want and that they must actually open).

If you setup Microsoft's Certificate Server and sign your controls yourself, then as long as your users install your certificate (a pretty automatic and one-time thing), you'll get past that hurdle.

But there's still another hurdle you may have to get over - the issue with marking controls safe for scripting.

Does your control contain any constituent controls (like a common dialog box or other vb control)? If it does, then depending on what the constituent control is, you may have to mark those controls safe for scripting; marking your own control safe may not be enough. This can be done with some code additions to your control and the inclusion of another file (I think it's a .TLB file, but I can't remember off the top of my head - got it at work though).

It might be easier for you just to change the user's security settings through pointing them to a page the opens a .reg file that contains the settings the way you want them. What I have done is to create a reg file that adds my site to the "Trusted Sites" zone and changes the settings on this zone to very low security.

Hope this helps.