Sanitized details from Certificate issuer field:
E = dmchenry@<removed>.com
CN = deltatao.com
OU = Main
O = Deltatao
L = Citrus Heights
ST = CA
C = US
When will the site be up with a valid certificate?
It's self signed. and thus, not to be trusted. Certs aren't that expensive. I think someone posted a link to cheap and valid certs. Could someone with that info chime in and maybe send Eldon a message?Jeanne wrote:What's wrong with that certificate?
Looks like you got a non-wildcard cert -- it matches to deltatao.com but not www.deltatao.com. You should add a redirect to remove the www when using SSL.Joedelta wrote:Better now?
Do people really feel this way about all SSL certs?noivad wrote:It's self signed. and thus, not to be trusted. Certs aren't that expensive. I think someone posted a link to cheap and valid certs. Could someone with that info chime in and maybe send Eldon a message?Jeanne wrote:What's wrong with that certificate?
Well a self signed certificate isn't worth the bits it is imprinted in. As long as people know you self signed for an FTP or other non-web site, and that there's a chance this info could be faked, then go ahead.Aldernon wrote:Do people really feel this way about all SSL certs?noivad wrote:It's self signed. and thus, not to be trusted. Certs aren't that expensive. I think someone posted a link to cheap and valid certs. Could someone with that info chime in and maybe send Eldon a message?Jeanne wrote:What's wrong with that certificate?
I've only ever bowed to, what I see as the extortion of the CA's, when adding a cert to my company's secure web server. I still use self-signed certs for my ssl ftp server and my ssl vpn device(s).
I'm honestly curious what peoples views are on this...the only place I can see it as useful is for http(s) traffic.