Just want encryption. Do I need Server Cert?

I have a web-based application on the Internet.  I want to secure the data transmission between web server and client's browser.

My web server support SSL on port 443.

Since obtain a Server Cert from CA need money, to save my wallet, is necessary to have a server cert for encrypting data over Internet? (or, how can I have a server cert freely & easy?)

Please advise.  Thanks.
Who is Participating?
Jason_DeckardConnect With a Mentor Commented:

A server certificate is needed for SSL (HTTPS).  You can either purchase a certificate from a well-known Certificate Authority (CA), or you can create a self-signed certificate (you are the CA in this case).

The issuer of a certificate (the CA) must be trusted by the client in order for the SSL handshake to succeed.  Clients trust CAs by installing the CA's certificate (also known as a "Trusted Root Certificate") into their browser.  Popular browsers, such as IE, Netscape, and Konquerer, have many Trusted Root Certificates built into them.  This allows end-users to successfully negotiate HTTPS and other SSL sessions with websites that use certificates from the well-known CAs, such as Verisign and Entrust (plus many, many others).

The advantage of purchasing a certificate from Verisign (or other well-known CA) is your client's browsers will automatically trust your server certificate without any sort of intervention on their part.  The disadvantage is cost.  Certificates can cost hundreds or thousands of dollars, and you must renew them annually.

The advantage of creating a self-signed certificate is the cost savings.  The disadvantages are:  1) having to maintain your own CA.  2) having to convince your users to install your Trusted Root Certificate.  3) having to (in some cases) teach your users to install Trusted Root Certificates.

The choice to go with a self-signed certificate or one issued by a well-known CA is yours.  In the end, you must decide between spending more money or spending more time.

Please let us know if you have any further questions about SSL certificates.

Jason Deckard
liddlerConnect With a Mentor Commented:
A server cert is a way of saying CA definately says this secure server is you.  The cert doesn't make the traffic any more encrypted, it is about stopping other people spoofing your site
The web page https://www.fortify.net/sslcheck.html will tell you what sort of SSL your web browser can support.  https://www.fortify.net/README_main.html#check explains what it actually does and other ways to verify what level of SSL connection you're getting.  (Ignore the guff on Netscape).

If you want a CA for your web site, check out http://slwww.epfl.ch/SIC/SL/CA/
or possibly http://www.entrust.com/freecerts/webcerts/ca_cert.htm
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

Thawte is a much lower cost alternative CA is using IIS

You might also consider a VPN for a limited audience if you're running a ms server or your router has the cabability.
lmoore has you in the right direction if using IIS. Are you running Application Server?
saikitAuthor Commented:
My webserver is Apache.  If I don't have a server cert from public CA, will the client's browser prompt a dialog box about I don't have a good server cert?

You could issue your own certificate
( see http://www.bigbiz.com/docs/CA.html )

The issue is "Does the client trust the certificate authority"
Normally when someone does business on the web, they can see that the issuer is Verisign, Thawte, etc... a concern that verified the identity of the certificate holder. Privately issued certificates are routinely used on intranets, as the client trusts the company they're working for.

You can get a public certificate for as little as $35.
You have to have a registered DNS name and the certificate is tied to that.
saikitAuthor Commented:
Dear Experts,

Thanks for the rich of info, I think I need to build my own CA.  May I know more: I just concern that how will end-users find the different between my own CA and well-known CA?

(Any dialog will be promoted? or May I have two URLs example about using private CA and well-known CA?)
Clients must import your root certificate. The root certificates of the major CA's are usually already present in your browser's distribution files. You may notice they expire from time to time and new ones have to be installed.
The normal way to do this would be to put it on the server at port 80 and point them to it.


Here's an example of a small CA's web page for doing this:

and a howto for openssl:
did these comments answer your question?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.