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.

I think the biggest mistake many of us make when we set out to build a website to make money is not to think out clearly how we are going to achieve this under our given set of circumstances.

We immediately jump on whatever bad wagon promises the best opportunity and hope to be able to achieve the same results. While hope is always nice it is action that will bring results. This is why it is imperative at the outset for you to figure out what you are prepared to do and how you are going to go about doing it.

For example list your strengths and what you are comfortable doing. Then you are going to look for ways and opportunities that will compliment your strengths.

If I had done this years ago I would have been a lot more successful. What I did instead was jump on the latest greatest opportunity, then when I would get the material I would be disappointed because many of the techniques listed where not in my field of expertise.

For example it would involve me having to cold call people to make sales and this is something I hate to do. So your first objective when setting out to build a website is to build it around a subject that you have some relationship with. Basically something that interests you.

Start out broad and be prepared to be taken down different paths that may yield more positive results in other words do not be too ridged.

Research is critical the more time spent researching the better your chances of success. Visit forums relative to your topics of choice and see what people are looking for - then with this information start to structure your site.

There are many site builders out there that can help. The one I used took care of the hosting and also helped me to market the site. This was very helpful especially starting out.

To conclude figure out what you want to do then be prepared to be adaptable based upon what the market demands. Then build a site that addresses their needs and provides solutions and you will make money.

Most web development projects include one or more of the following elements...

• Database design and creation
• Server-side computer programming
• Client-side computer programming
• Web page design

Each of these elements has to work in its own right, and in cooperation with the other elements. The more complex the project, the harder it is to bring it all together and make it work correctly.

How to keep the cost down

Here's how you can make sure your web development costs don't run over budget...

1. Insist every aspect of the development is described in an Agreement document, and make sure both you and the developer sign it
2. Don't make changes after work has started

The key to achieving the second of these two items lies with the first. You should insist that an Agreement document be created, and sit in on the process.

You need both end-users and developers in the same room, working through each aspect of the development. The end result must be a document that fully describes the development, is clear (unambiguous), and easily understood by both users and programmers.

Every minute you invest creating this document greatly increases your chance of bringing the project in on budget.

Why it's worth it

Many of the problems that usually cause headaches during a complex development could have been discovered in advance, if an Agreement document had been created. When users and programmers get together and discuss their respective needs thoroughly, the resulting development is far more likely to go smoothly.

This kind of interaction forces both users and programmers to think through what's actually required to make the system work. The ongoing interaction reduces the risk that person A assumes person B knows what they're talking about.

Users are committing to a specific set of functions for an agreed price. The developer is committing to develop those functions for an agreed price. This means both users and developers have a self-interest in being thorough.

Should a user change his/her mind about something after the Agreement document is signed, the cost of development must be renegotiated. This punishes the user for failing to think things through.

Should the developer discover he/she hasn't fully understood what's required to complete some aspect of the project, he/she can't ask for more money. This punishes the developer for failing to break down each stage of the development and understand what's involved in completing it.

Assuming you do your part, you won't need to make changes after the work has started. As a result, you'll bring the project in on budget even if the developer hasn't done his/her job properly.