Anyone can generate a certificate, the question is, who will trust it. If
you are using certificate between your computer A and your computer B, you
generate your own certificate and tell A and B to trust it. But you can't
force others to trust it. Others trust commonly-known certification
aithorities, so called root certificates, and down the tree from them. So
3rd party can be expected to trust only certificate that belongs to that
tree - yours does not.
From
http://en.wikipedia.org/wiki/Certificate_authority
"...the market for SSL certificates (used for website security) is largely
held by a small number of multinational companies. This market has
significant barriers to entry since new providers must convince web browser
developers to include them in the list of trusted authorities in future
versions of the browser, and there is no automated means to add trusted
authorities to older versions. Thus there is an effective oligopoly of
approximately 20 root certificates that are already trusted in the most
popular versions of the most popular web browsers. "
Vadim Rapp
Polyscience
www.polyscience.com
"Herb" <stullhe104@newsgroup.nospam> wrote in message
news:255C7662-C123-4A79-8185-172C7AECDEA1@microsoft.com...<span style="color:blue">
>I currently use a digital certificate generated from my domain server to
> authenticate connections to ISA Server and encrypt traffic between
> site-to-site VPNs.
>
> Now I need an SSL cert to use for a website. Can I generate that from my
> domain server also? If so, how does this compare to an SSL cert that you
> purchase from a third party vendor?
>
> Thank you, stullhe104
> --
> stullhe104 </span>