Ben Kennedy wrote: [clip] > My fundamental simple question on the subject: given that > it's so easy (and cheap, i.e., free) for me to provide secure > shell access to my clients, how can I do the same for HTTP > connections, without having to pay money to a third party > that neither of us particularly cares about?
You can always self-sign certificates for free. These however will require that your customers add your certificate to their list of trusted certificates in their browser or they will get a warning when they access your site... -t
winmail.dat
Description: application/ms-tnef
