Atl ActiveX网页控件的数字签名和安全验证

项目需求中,有需求:从Javascript中生成ActivexObject对象,然后调用其方法和响应其事件。例如:

<script language="JavaScript" type="text/javascript">
<!--
        var assistantCtrl = new ActiveXObject("myActivexCtrl.progId");       
        assistantCtrl.sayHello("hello");
// -->
</script>

 但是new ActiveXObject("myActivexCtrl.progId"); 总是失败。分析原因为:IE7对未加数字签名的 ActiveX dll文件采用的安全策略,不允许生成对象和调用。经过对IE7的安全策略的修改,调为最安全级别最低,则正常。或者在中级安全时,设置可以下载和运行为签名的ActiveX控件也可以。

 我的开发环境为:开发主机Windows XP, VS2008 做的ATL Com ActiveX控件(已经注册成功并且从其他VC项目中能调用),  IE7.

 

尝试一1:在我的控件安装.exe中,将该网站设置为授信网站,只需要修改注册表即可。结果失败。

 

尝试—2:数字签名

于是,从网上找到免费签名工具signcode.exe,制作cer整出,pvk私钥,和spc文件,支持在设置时间戳url的地方没有勾选,最后给dll签名成功。但是IE7的加载应用的列表里,我的控件发布者还是 (未验证)控件名 的样子。数字签名只把控件名显示出来了,以前是未知名称。于是测试,还是失败。网上有人分析,是因为时间戳url没有指定,或者指定的url和你的证书不匹配。网上有人提供免费的时间戳url,但是也要用他们的证书来签名才可以用。

 

尝试—3:

于是另辟蹊径,查看MSDN,看到我们的ATL 或者 MFC的ActiveX控件,只要实现了IObjectSafety接口就可以不用数字签名。于是给我的Atl Com类加上:

 

头文件中让你的类继承:

public IObjectSafetyImpl<CYourComClass,INTERFACESAFE_FOR_UNTRUSTED_CALLER|INTERFACESAFE_FOR_UNTRUSTED_DATA>,

然后在下面的EGIN_COM_MAP加上对IObjectSafety的包含,如下:

EGIN_COM_MAP(CYourComClass)
    COM_INTERFACE_ENTRY(IYourComClass)
    COM_INTERFACE_ENTRY(IDispatch)
    COM_INTERFACE_ENTRY(IObjectSafety)
    COM_INTERFACE_ENTRY(ISupportErrorInfo)
    COM_INTERFACE_ENTRY(IConnectionPointContainer)
END_COM_MAP()

 

经过测试,就算没有数字签名和设置授信网站,IE7会提示用户是否使用该ActiveX控件,显示的为未知发行商。至此,该ActiveX控件已经通过了IE的安全拦截,如果想修改发行商名称,使用方法2中的数字签名工具给dll签名即可,但是你的公司名称前,还有未验证的字样。

 

其他深入的问题还没有经过研究。有朋友发现可以告诉我。

  • 0
    点赞
  • 2
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
需要用来获得所需的功能在步骤涉及到 IObjectSafetyImpl 用作您的件派生的类之一,和重写 GetInterfaceSafetyOptions 和 SetInterfaceSafetyOptions。 这使您实现所需的功能在这种情况下意味着将标记为可安全编写脚本和初始化该件。 若要将 IObjectSafetyImpl 需要将其添加到您的件派生的类的列表。 是例如多边形教程中您看到以下: class ATL_NO_VTABLE CPolyCtl : ... public IObjectSafetyImpl // ATL's version of // IObjectSafety { public: BEGIN_COM_MAP(CPolyCtl) ... COM_INTERFACE_ENTRY_IMPL(IObjectSafety) // Tie IObjectSafety // to this COM map END_COM_MAP() STDMETHOD(GetInterfaceSafetyOptions)(REFIID riid, DWORD *pdwSupportedOptions, DWORD *pdwEnabledOptions) { ATLTRACE(_T("CObjectSafetyImpl::GetInterfaceSafetyOptions\n")); if (!pdwSupportedOptions || !pdwEnabledOptions) return E_FAIL; LPUNKNOWN pUnk; if (_InternalQueryInterface (riid, (void**)&pUnk) == E_NOINTERFACE) { // Our object doesn't even support this interface. return E_NOINTERFACE; }else{ // Cleanup after ourselves. pUnk->Release(); pUnk = NULL; } if (riid == IID_IDispatch) { // IDispatch is an interface used for scripting. If your // control supports other IDispatch or Dual interfaces, you // may decide to add them here as well. Client wants to know // if object is safe for scripting. Only indicate safe for // scripting when the interface is safe. *pdwSupportedOptions = INTERFACESAFE_FOR_UNTRUSTED_CALLER; *pdwEnabledOptions = m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_CALLER; return S_OK; }else if ((riid == IID_IPersistStreamInit) || (riid == IID_IPersistStorage)) { // IID_IPersistStreamInit and IID_IPersistStorage are // interfaces used for Initialization. If your control // supports other Persistence interfaces, you may decide to // add them here as well. Client wants to know if object is // safe for initializing. Only indicate safe for initializing // when the interface is safe. *pdwSupportedOptions = INTERFACESAFE_FOR_UNTRUSTED_DATA; *pdwEnabledOptions = m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_DATA; return S_OK; }else{ // We are saying that no other interfaces in this control are // safe for initializing or scripting. *pdwSupportedOptions = 0; *pdwEnabledOptions = 0; return E_FAIL; } } STDMETHOD(SetInterfaceSafetyOptions)(REFIID riid, DWORD dwOptionSetMask, DWORD dwEnabledOptions) { ATLTRACE(_T("CObjectSafetyImpl::SetInterfaceSafetyOptions\n")); if (!dwOptionSetMask && !dwEnabledOptions) return E_FAIL; LPUNKNOWN pUnk; if (_InternalQueryInterface (riid, (void**)&pUnk) == E_NOINTERFACE) { // Our object doesn't even support this interface. return E_NOINTERFACE; }else{ // Cleanup after ourselves. pUnk->Release(); pUnk = NULL; } // Store our current safety level to return in // GetInterfaceSafetyOptions m_dwSafety |= dwEnabledOptions & dwOptionSetMask; if ((riid == IID_IDispatch) && (m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_CALLER)) { // Client wants us to disable any functionality that would // make the control unsafe for scripting. The same applies to // any other IDispatch or Dual interfaces your control may // support. Because our control is safe for scripting by // default we just return S_OK. return S_OK; }else if (((riid == IID_IPersistStreamInit) || (riid == IID_IPersistStorage)) && (m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_DATA)) { // Client wants us to make the control safe for initializing // from persistent data. For these interfaces, this control // is safe so we return S_OK. For Any interfaces that are not // safe, we would return E_FAIL. return S_OK; }else{ // This control doesn't allow Initialization or Scripting // from any other interfaces so return E_FAIL. return E_FAIL; } } ... } ATL 3.0 中, IObjectSafetyImpl 的实现已更改,使您现在可以作为模板参数提供安全选项。 例如,上述类的声明将显示为 class ATL_NO_VTABLE CPolyCtl : ... public IObjectSafetyImpl { public: BEGIN_COM_MAP(CPolyCtl) ... ,您将不必重写两个方法。 有关其他信息,单击下面,文章编号,以查看 Microsoft 知识库中相应: 192093 PRB: 编译器错误时移植到 ATL 3.0 IObjectSafetyImpl
评论 2
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值