Mr. Hat..err... Gothi[c],
One reason you don't see as much (https) encrypted websites on the web as you should is because of a limitation in the https protocol: only one https domain name per ip address is possible.-Gothi[c]
Just using my intuition, I wouldn't guess that as one of the reasons. What are you basing your statement on? Strictly going on personal experience, I don't think there is a lack of use of SSL. I don't always pay attention, but just about any website I use that requires the transfer of data of a personal nature uses an SSL connection. (Don't forget that the page with the form may be served up w/o SSL and the page you see after submission may be served up w/o SSL, but the forms data can still be sent via https.)
The number one problem, IMNHO (In My Never Humble Opinion) is that geeks rule the internet. They build stuff that makes sense to them, not "normal" people. The #1 problem in that geeks expect other geeks to "comply" and "understand" the technical issues and so build things that way. Let's continue on the example of HTTPS. Geeks may understand why warning boxes pop-up and warn about SSL certs and hostnames not matching ip addresses and domains having expired and crap like that. But what does the average user do? The exclaim, "WTF is this?" and then click through the error box and go to the page anyways. Why? Because they have done it before and the world didn't end. Why did they do it before? Because some sysadmin goofed up in the past and the cert was invalid for 24 hours on some site the user trusted. When the user went to that site during that 24 hour period they saw the warning box, didn't understand the technical details, clicked through, and all was well.
I don't know what the solution to such problems are, but I doubt they are purely technical.
Recent Posts
I'm going to use it... as soon as I can find somebody who would get the joke. 
