×
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.
<snip>
the relay-host doesn't require certificates from a certificate authority
</snip>
...yet.
<snip>
Same with true for web services. Web service clients and servers don't
mess
with certificate authorities.
</snip>
... yet, at least to the best of our knowledge.
<snip>
Why do browsers?
</snip>
Do you care? Or are you hoping that this discussion single handedly
changes all browsers, standards organizations, audit firms, etc to change
back to allowing self signed certificates?
If we continue to reply are your answers going to continuly bounce back
between browsers and mail relays and keep arguing?
I'll try, once. Stick to the browser example.
I create a website. I call it IBM.COM. I use a self signed certificate
which says I am IBM.COM. I do dns poisoning so that when you route to
IBM.COM from your particular ISP you end up going to my website. You're
using a crappy browser which allows self signed certificates and doesn't
even flag it as such, or, you answer to accept self signed certificates so
often you get numb to it and no longer care.
Apparently FTPS is also starting to care. Using a self signed certificate
was rejected when I tried to use FTPS with IBM today.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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
