Ask Josephsen <ask_rem@rem_minreklame.dkwrites:
I've got at website that needs to run https and I understand you
need to purchase an SSL certificate to do so. But what is a fair
price and does it matter from who I buy and what I buy?

it is also possible to generate your own self-signed SSL certificate
and have clients that need to access your site validate the
certificate via some out-of-band process.

i regularly access some number of https sites with self-signed
certificates where my browser initially complains it is signed by
an unknown certification authority (itself) and gives me an
opportunity to view it, accept it for the current session, and/or load
it for long term acceptance (basically into the same repository that
contains the certification authority self-signed digital certificates
that were loaded as part of building the browsers).

if you really want to buy one go to the security menu in the
browsers (that will be typically used by your clients) and do a list
of the currently loaded self-signed digital certificates this will
give you an indication of which certification authorities that the
browsers are currntly configured to automatically accept.

numerous collected past postings mentioning ssl and ssl digital
certificates
http://www.garlic.com/~lynn/subpubkey.html#sslcert

Ask Josephsen <ask_rem@rem_minreklame.dkwrites:
I've got at website that needs to run https and I understand you
need to purchase an SSL certificate to do so. But what is a fair
price and does it matter from who I buy and what I buy?

it is also possible to generate your own self-signed SSL certificate
and have clients that need to access your site validate the
certificate via some out-of-band process.

i regularly access some number of https sites with self-signed
certificates where my browser initially complains it is signed by
an unknown certification authority (itself) and gives me an
opportunity to view it, accept it for the current session, and/or load
it for long term acceptance (basically into the same repository that
contains the certification authority self-signed digital certificates
that were loaded as part of building the browsers).

if you really want to buy one go to the security menu in the
browsers (that will be typically used by your clients) and do a list
of the currently loaded self-signed digital certificates this will
give you an indication of which certification authorities that the
browsers are currntly configured to automatically accept.

numerous collected past postings mentioning ssl and ssl digital
certificates
http://www.garlic.com/~lynn/subpubkey.html#sslcert

Anne & Lynn Wheeler <lynn@garlic.comwrites:
i regularly access some number of https sites with self-signed
certificates where my browser initially complains it is signed by
an unknown certification authority (itself) and gives me an
opportunity to view it, accept it for the current session, and/or load
it for long term acceptance (basically into the same repository that
contains the certification authority self-signed digital certificates
that were loaded as part of building the browsers).

the real major difference between a self-signed digital certificate
that you generate and a self-signed digital certificate generated
by some certification authority it that the certificate
authorities have convinced the browser vendors (typically by paying
them) to preload their digital certificates into the browser's digital
certificate repository when the browser is built.

however, it is straight-forward operation for clients to do
post-install administrative operations on their browser's digital
certificate repository (adding and/or deleting digital certificates).