Usual HTTP connections are not encrypted. This results in the fact that anybody, able to intercept the data packets on the wire, is able to read their content. Same with possibly transferred passwords. To protect such connections from getting monitored by a third party there are Secure Socket Layer. Thereby an encrypted connection is beeing established from both communication parties, which is used for transferring the data afterwards. In case of HTTP this means that the browser establishes such an encrypted channel with the webserver.
In order to let the browser know it is talking to the correct communication partner - the person willing to intercept this communication could pretend to be the webserver ("Man-In-The-Middle"-Attack) - the webserver possesses a certificate to identify itself to the client. Such a SSL certificate is bound to the URL URL of a webserver.
Availability of certificates
A SSL certificate is issued by different service providers on an identification evidence. This evidence is necessary, because otherwise anybody could apply for a certificate for e.g. eshop.bytemine.net
Services of bytemine around SSL
bytemine offers the following services around SSL:
- Issuing CACert SSL certificates
- Consulting and support on buying SSL certificates
- Configuration of your webserver for the use with SSL certificates
- Webhosting with SSL support
Additionally we gladly sign your PGP respectively GPG key.