An SSL, or Secure Socket Layer, is technology that has been developed that allows web browsers and web servers to communicate over a secured connection.

The system uses cryptography that uses two keys to encrypt data  a public key known to everyone and a private or secret key known only to the recipient of the message. It’s a way to encrypt data, like credit cards numbers (as well other personally identifiable information), which prevents the "bad guys" from stealing your information for malicious intent.

The recently introduced SSL v3 improved upon SSL v2 by adding SHA-1 based ciphers, and support for certificate authentication. SSL v2 was known to be flawed in a variety of ways. Identical cryptographic keys are used for message authentication and encryption. The older version did not have any protection for the handshake, meaning a Man-in-the-middle downgrade attack could go undetected.

SSL has recently been succeeded by Transport Layer Security (TLS), which is based on SSL and is included as part of both the Microsoft and Netscape browsers and most Web server products. SSL uses the public-and-private key encryption system from RSA, which also includes the use of a digital certificate.

SSL-enabled client software can use standard techniques of public-key cryptography to check that a server's certificate and public ID are valid and have been issued by a certificate authority (CA) listed in the client's list of trusted CAs. Client authentication allows a server to confirm a user's identity. It’s a way to assure a client that they are dealing with the real server they intended to connect to. It can prevent any unauthorized clients from connecting to the server, preventing anyone from meddling with data going to or coming from the server.

From the very beginning SSL was designed to provide security between client and server, and to avoid any kind of 3-way man-in-the-middle attack.

Conceptually it’s quite simple: it negotiates the cryptography algorithms and keys between two sides of a communication, and establishes an encrypted tunnel through which other protocols (like HTTP) can be transported. It can also be easily passed through firewalls and proxies, as well as through NAT (Network Address Translation) without issues.

Hello

I am a person who decided 3 years ago that I wanted to create or build my own websites.

The company I use to assist me not only has ALL the tools and All the advice and ALL the assistance and can prove ALL that it says and is SO cheap to purchase, just today it surprised me AGAIN.

It appears that they had a little setback with one of the tools they provide. This tool is a major tool for all of us who are building websites.

Did they deny the problem? No.
Did they try to pass the blame onto someone else? No.
Did they try to hide from a lot of angry customers? Again, no.

Here is what they did.
They sent an email out to everyone, yes that's right everyone telling us that there was a problem AND APOLOGIZING PROFUSELY!

In addition they compensated us for the inconvenience by adding credits to the tool that was affected.

They kept in contact with us all through a forum which was very easy to locate and use.

They received many, many words of encouragement from a lot of website builders basically saying - thanks for the extra credits and no problem with the glitch.

Then the company advised after many testings that the problems were all fixed and we were good to go.

NOW IS THIS THE TYPE OF SERVICE YOUR COMPANY PROVIDES?

I'm reasonably confident that a lot of people are paying a lot of money for a product which does NOT do all that this particular company does. Question is why do so many people stay with that type of website building company?

The thing about computer languages is that there is some weird heaviness on the actual work involved. People are scared of by codes and although they see the power, they just can't seem to get going because they have no idea where to start.

That is where training comes in. And of course, fun training. You need to be taken by hand and shown exactly what you need to do, where you need to do it, and when you need to take the right action.

The funny thing about CSS is that it allows you to create your website in the fraction of the time when you would do it using tables. It's hard to believe, but still after all these years of promotion for CSS people (and companies!) still heavily rely on tables for layout. They have no idea that they are simply wasting time on old techniques that will be useless in a matter of time.

So where do you need to pay attention on when you are looking for a CSS Guide?

1. The Teacher

The number one thing you need to be sure of is that your teacher knows where he or she is talking about. Why is he or she teaching about Cascading Stylesheet, because they need to from their boss? Because they think they can teach, no matter the subject?

Think of that, how many teachers are only "teaching" stuff, and never practice it their own? Ask yourself "why" are you teaching you me this. Are you the best in the field? Where did you get your knowledge from?

2. Teaching Style

So the teacher may be a great person, has all the required skills, has a passion for the subject and knows about everything of it. But can your teacher deliver? Does he or she KNOW how to explain things? How to take you by hand and show you step-by-step how things work?

Is it fun to follow along with the teacher? CSS is one of those topics that can become boring easily when it's only discussed in a technical way. Make sure you know what you can expect!

An even more important thing is cutting right to the case. You don't want to end up with all kind of knowledge that you will never use in practice. It simply isn't useful to learn every possible css style there is when you just get started. And this brings us to the third point you need to pay attention on when you are looking for a css guide.

3. Teaching / learning speed

Can you keep up with the course? Does your teacher decide the speed, or do you? Of course a great way to follow a course is one that allows you to define your own speed. Home study courses and guides are wonderful for that.

4. Delivery

How is your guide delivered? Are you somebody that likes to read, follow along with a training video or both? Decide what you like, training videos are great, because they allow you to follow along in a real life situation. This means hands on practice, which is exactly what you need if you want to become good in CSS.

5. Contents

Last but not least, content. What is discussed in the guide? What is marked as important? Do you get a total reference, or do you know you don't need that, that the real thing you need is a hands on course with day-to-day subjects? Decide what you want to know, just the basics, how to create full layouts, or just how to create a menu using 100% CSS.

It's up to you now, decide what you need, you know how important the 5 above points are, and where you need to pay attention on. And one last tip, make sure you get some preview videos or sample chapter before following any course, it can save you a lot of time and money at the same time.

Hilco van der Meer
CSS Expert