×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Different organizations are comfortable with different levels of risk.
Sometimes they just want the session encrypted. Sometimes they want to
authenticate the server. At various different levels of authentication.
Sometimes they want full client and server authentication. Even then
it's not 100% secure.
Consider John's (the OP) example. He wants to connect programmatically
to a PC that has a certificate not issued by a public CA, and where the
CN doesn't match the machine. He still benefits from an encrypted
session. Presumably, he feels that the IP address is a good enough
check to make sure he's connected to the right machine. Indeed, it
might be, if this is a private and controlled network.
Seems to me that it's up to each organization to decide what level of
risk they're willing to accept. Providing flexibility in the software
is a good thing.
On 4/23/2010 1:29 PM, Lukas Beeler wrote:
If you don't check the certificate, why use SSL at all?
Anyone will still be able to easily and trivially do a MITM attack.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
