I'm kinda confused. If SSL certificates help to indentify that you are connected to a trusted server, then why is it necessary to use an encrypted ( HTTPS ) connection ? Can I use SSL certificates for HTTP connections?
相关问题
- Mechanize getting “Errno::ECONNRESET: Connection r
- Can ServiceStack JsonServiceClient send a get requ
- Tomcat and SSL Client certificate
- Can we add four protocols to ServicePointManager.S
- .NET Core gives unknown error while processing HTT
相关文章
- 请大神帮忙 post向https接口发送数据 部署到服务器为什么运行一会后就会报空指针
- ssl配置问题
- Intermittent “sslv3 alert handshake failure” under
- Making a two way SSL authentication between apache
- decrypt TLS 1.2 AES-GCM packet
- How to use Jetty with Let's Encrypt certificat
- Sending email using php, gmail, and swiftmailer ca
- Can't pip install packages in python 3.6 due t
There's a misconception here. Certificates are not SSL. It's SSL that uses certificates, but certificates were born before SSL. Consequently yes, you can use X.509 certificates without SSL (you can sign the request and put the signature to, for example, HTTP headers). You can use certificates with SSL but without SSL encryption (some of NULL ciphersuites).
The convenience of SSL/TLS is that it's a standard, i.e. it's widely recognized and strictly defined, while with other schemes you'd need to implement something homemade. Yet I can remind you of WS-Security standard which does exactly what you are asking about -- when you send the request to the web server via HTTP and utilize WS-Security, you get certificate authentication without SSL (via plain HTTP).