I WOULD LIKE TO KOW WHEN PART 2 BE AVAILABNLE??
I don't think most web browsers, such as IE and Firefox, will trust the root certificates from StartCom and will pop up warnings that it's can't verify the authenticity of the SSL cetificate. IE and Firefox expect certificates from Verisign, Thawte, or e-Trust, and will annoy the end user with other non trusted certificates. I can just as easily publish my own X.509 certificate by setting up a CA on one of my Windows 2003 servers to SSL enable OWA, but the annoying security popups on the browsers will raise suspicions among those using it. I agree that not having to pay for a public root certificate is a great idea, but if the web browsers will reject it, then what good is it?
- Keyboard Shortcuts: