如何配置 WinCE 以使用通配符 SSL 证书?
我们的 Windows CE 5.0 应用程序的通配符 SSL 证书 (*.domain.com) 存在问题 - 它不会将其视为有效。
我知道 Windows Mobile 6.0 支持通配符证书(早期版本不支持),并且它是基于 WinCE 5 构建的,这表明应该可以更改 WinCE 5 以接受通配符证书(编辑 - 显然这表明我对通配符证书的理解有限)环境,不是一个有效的假设!)。
谁能建议我们如何解决这个问题? 更改需要是程序化的,以便我们可以将其推广到数百个现有客户。
帮助!
Our Windows CE 5.0 application has a problem with our wildcard SSL certificate (*.domain.com) - it won't accept it as valid.
I understand that Windows Mobile 6.0 has support for wildcard certificates (earlier versions don't) and that is built on WinCE 5 which suggests it should be possible to change WinCE 5 to accept wildcard certificates (EDIT - apparently this shows my limited understanding of the environment and isn't a valid presumption!).
Can anyone suggest how we go about this? The change needs to be programmatic so that we can roll it out to hundreds of existing clients.
Help!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
这将接受所有证书,并根据需要进行修改。
System.Net.ServicePointManager.CertificatePolicy = new TrustAllCertificatePolicy();
This will accept all certs, modify as needed.
System.Net.ServicePointManager.CertificatePolicy = new TrustAllCertificatePolicy();
为什么 WinMo 支持它们的事实表明 CE 5.0 也会支持它们? 你需要明白CE是一个模块化的操作系统,平台的很大一部分是由平台OEM编写的。 WinMo 的平台 OEM 是 WinMo 团队。 WinMo 团队可能自己编写了支持并将其添加到他们的平台中,就像 WinMo 中的所有 UI 元素在普通 CE 中不存在一样。
从历史上看,微软倾向于将至少一些功能从WinMo平台引入到随后的CE版本中(例如aygshell,它出现在PPC(基于CE 3.0和4.2)中,并且仅在他们开发之后才出现)它是否包含在通用 CE (5.0) 中。
值得研究一下 CE 6.0 是否支持通配符证书,如果支持,请考虑迁移您的平台 BSP。如果不存在,则需要您编写(或购买)。支持并自行将其添加到您的平台。
Why would the fact that WinMo supports them suggest that CE 5.0 would? You need to understand that CE is a modular OS, with a large part of the platform written by the platform OEM. The platform OEM for WinMo is the WinMo team. The WinMo team has likely written the support themselves and added it to their platform, just like all of the UI elements in WinMo that don't exist in vanilla CE.
Historically Microsoft tends to pull at least some features from the WinMo platform into CE releases that come after (like aygshell for example, which appeared in PPC (based on CE 3.0 and 4.2) and only after they developed it was it included in generic CE (5.0).
It would be worth investigating to see if CE 6.0 supports wildcard certs, and if so looking at migrating your platform BSP. If it's not there, it's going to require that you write (or buy) the support and add it to your platform yourself.