安全 ODBC 连接——矛盾？
有时我们需要通过“管道”创建到我们客户站点之一的 ODBC 连接。 我们希望为我们的客户提供尽可能多的安全性，因为我们使用的是 ODBC，而且……
无论如何，SQL Server DSN 中有一个复选框设置，上面写着“对数据使用强加密”，但绝对没有其文档。 我在谷歌网上能找到的唯一参考资料都是未解答的问题——不太令人鼓舞。 有人知道它的作用或工作原理吗？ 如果这不是加密数据流的方法，还有其他方法吗？
顺便说一句，我们不能依赖我们的客户从他们的一端强制加密，处理安全证书将是一场真正的噩梦。
提前致谢， 戴夫
There are times we need to create an ODBC connection over the "tubes" to one of our customer sites. We would like to provide as much security as possible to our customers, given we are using ODBC and, well...
Anyway, there is a checkbox setting in the SQL Server DSN that says "Use strong encryption for data", but absolutely no documentation for it. The only references I can find on the Google nets are unanswered questions -- not very encouraging. Does anybody have a clue what it does or how it works? If that isn't a way to encrypt the data stream, is there another way?
BTW, we cannot rely on our customers to force encryption from their end, and dealing with security certificates would be a real nightmare.
Thanks in advance,
Dave
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
是 SQL 2000 还是 2005/2008？
加密强制可以由客户端请求或由服务器强制。 加密基于 Schannel 协议 (ssl)，因此需要在服务器上部署并受客户端信任的有效证书，这是没有办法的。 该证书必须由客户端信任的机构签名，并且除了其他典型的服务器证书要求之外，还必须将客户端用于连接的 FQDN 名称作为其主题。
在 SQL 2005 中如何：启用加密连接
在 SQL 2000 中 配置服务器 和客户端请求加密
Is it SQL 2000 or 2005/2008?
The encryption enforcement can be requested by the client or enforced by the server. The encryption is based on Schannel protocol (ssl) and as such requires an valid certificate deployed on the server and trusted by the client, there is no way out of that. The certificate has to be signed by an authority that is trusted by the client and, amongst other typical server certificate requirements, must have the FQDN name used to connect by the client as its subject.
In SQL 2005 How to: Enable Encrypted Connections
In SQL 2000 Configure the Server and Request encryption by client
使用 ODBC 时没有理由不能建立安全连接。 基本上，线上安全性的责任属于 ODBC 驱动程序（基本上是特定于数据库的部分）。 如果驱动程序尚未提供此功能（SQL Server 可能提供，也可能不提供 - 我不知道“对数据使用强加密”适用于什么），您可能可以添加自己的驱动程序。 一种可能性是创建一个 SSH 桥，例如使用 ssh -L。 我不知道这是否算作“噩梦”，但这可能是一种有效且相当简单的技术。
There is no reason you can't have a secure connection while using ODBC. Basically, the responsibility for over-the-wire security would fall under the ODBC driver (basically the database-specific part). If the driver doesn't already provide for this (SQL Server may or may not - I don't know what "Use strong encryption for data" applies to) you can probably add your own. One possibility would be to create a SSH bridge, e.g. using ssh -L. I don't know if this counts as a "nightmare", but it would probably be an effective and fairly simple technique.