SSL Certificates - Secure Server Certificates: Unterschied zwischen den Versionen

Version vom 27. Juli 2012, 03:55 Uhr

SSL certificates are generally utilized with ecommerce shopping carts, or anywhere you want to collect details from a user securely on your web site. If you use a secure server certificate with a form and that form emails the results to you maintain in thoughts that the email is not secure.

SSL (Secure Sockets Layer): Creates an encrypted link between a web server and a browser. CA (Certificate Authority): The vendor you will get the secure server certificate from...

What is SSL?

SSL certificates are generally utilized with ecommerce shopping carts, or anywhere you want to collect info from a user securely on your site. If you use a secure server certificate with a form and that form emails the results to you keep in thoughts that the email is not secure.

SSL (Secure Sockets Layer): Creates an encrypted link among a net server and a browser. CA (Certificate Authority): The vendor you will get the secure server certificate from CSR (Certificate Signing Request): A text file generated by a web server. A CSR looks like this:

-----Start NEW CERTIFICATE REQUEST-----

MIIDGgBNAGkAYwByAG8AcwBvAGYAdAAgAFIAUwBBACAAUwB

AG4AZQBsACAAQwByAHkAcAB0AG8AZwByAGEAcABoAGkAYwl

L0ygNwwNIvKLMPq4/LcUkZ9Oo4AssXW5mvvhHWGz2RWYRhrw8o

-----End NEW CERTIFICATE REQUEST-----

First, you want to decide whether or not to use your hosting shared SSL certificate if they offer you it. The URL to your shop will look something like:

https://theirserver.com/youruserid/your/path/to/shop.html

Or do you want to get your own SSL certificate? The URL will look like:

https://yourdomainname.com

If you decide to use your hosts' shared secure server certificate, then all you need to have to do is find out the path you need to have to use to call your files securely, and you will be on your way.

If you decide to get your personal SSL certificate, this is normally what happens.

You very first require to decide who you are going to get your SSL certificate from. It is a excellent concept to make confident your host supports your certain vendor. Some certificate authority vendors are:

* Thawte

* Verisign

* Comodo

* You can also assessment numerous vendors at a glance at WhichSSL

Just before getting your own SSL certificate, you will need to have to do some reading on what your selected Certificate pki solution Authority needs for a secure certificate, and you'll also want to come up with some documentation. There are numerous steps to purchasing a secure server certificate, once you have decided on a certificate authority vendor.

This is an overview, not written in stone. Each and every CA is distinct, so make positive you read their documentation and what they call for. Here is an concept of what they want:

All documentation that is requested need to match *specifically*. Secure certificate authorities will verify that your organization really exists, so they know they are issuing to the right company. You will need to have to prove that the Organization Name and the Domain name are in fact yours to use.

Steps you will be taking:

* Gather essential documentation

* Have your host generate a CSR

* Complete certificate authority on the web application

* Certificate authority will process your request

* Pickup and install your SSL certificate (generally an URL is emailed to you to download the secure server certificate)

* Depending on the vendor, it can take a handful of hours to a couple of days.

* Send secure certificate to host for installation. (Send in plain text)

When your net hosting provider receives this details they will produce the CSR and send it back to you in plain text. You then send it on to Verisign or Thawte, or whoever you have selected as your secure certificate authority. They will then generate a SSL certificate for you which you will send back to your host for installation. Your net host may charge a fee for installation in addition to what your SSL certificate vendor charges.

One thing to think about:

If you have decided to obtain token security your own SSL certificate, you will need to determine how you want your URL to be called. If you, as a rule, call your domain name in your coding as www.yourdomainname.com, then make certain you indicate this to your host when you request a CSR from them. If you do not, and you get the certificate for yourdomainname.com (without the www), this will trigger browser errors, creating the certificate seem insecure, and you will need to change your coding.

Constantly use yourself or your company as technical speak to.

How to tell if a website is secure?

Soon after you have browsed to a internet site securely utilizing https:// in the URL, appear on the lower right hand side of your browser. You ought to see a closed lock. This will tell you the site is secure.