Re: Self Signed Certificates?



Well, you can make them work by distributing the certificates and manually
adding them to the trusted roots store. If he is only talking about getting
a limited number of clients and servers working, this is probably a
practical approach. If he tries to scale it further than that, he'll
quickly learn to discover why a CA (or commercially procured certs) is so
valuable. :)

The tool makecert.exe is probably the thing he needs. It isn't as easy to
use as selfssl (from the IIS 6 resource kit), but it can make any kind of
self-signed cert.

Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Brian Komar [MVP]" <bkomar@xxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1f853ab92ffc88649896c6@xxxxxxxxxxxxxxxxxxxxxxx
In article <v4KdnatGr9M30obYnZ2dnUVZ_rqdnZ2d@xxxxxxxxxxxx>,
westes-usc@xxxxxxxxxxxxxx says...
Is there a third party commercial or shareware tool to create self-signed
certificates under Windows 2000 and Windows 2003? My immediate need is
for
authentication on just a few servers and clients, and I don't want to
hassle
with certificate authorities (yet). I know there is a tool included in
IIS, but it doesn't work on machines that don't have IIS so it is not a
solution for us.


Self signed certificates will not work in the scenario you describe, as
they would not be
trusted by any of the other clients and servers.
Brian


.



Relevant Pages

  • Re: security header is not present in the incoming message
    ... One certificate "Client Private.pfx" to Certificates - Current User, Personal, Certificates. ... One certificate "Server Private.pfx" to Certificates - Current User, Other People, Certificates and the third one "Server Public.cer" to Certificates, Personal, Certificates. ... And this goes for services run in IIS och in ASP.NET Development Server. ...
    (microsoft.public.dotnet.security)
  • Unable to install certificates and unable to patch
    ... We have three terminal servers that we are not able to install MS ... Timestamping CA" certificates. ... When specify it to put them into the Trusted Root Certificate store I get ...
    (microsoft.public.windows.server.general)
  • Terminal servers missing required certificates
    ... We have three terminal servers that we are not able to install MS ... Timestamping CA" certificates. ... When specify it to put them into the Trusted Root Certificate store I get ...
    (microsoft.public.security)
  • Re: Multiple web hosts and SSL
    ... It is possible to create a "wildcard" cert using the name *.domain.com ... though there may be some limitations on which browsers [or servers?] can use ... packs had problems with wildcard certs, until service pack 1 or later was ... The price is not the same as non-wildcard certificates... ...
    (microsoft.public.inetserver.iis.security)
  • Re: Generation of certificate using openssl
    ... >>You could just use the Certificates Services that comes with Windows 2000. ... I'd hate to think that IIS and OpenSSL-created ... > The OP obviously has some business reason to use OpenSSL on his CA - perhaps ...
    (microsoft.public.inetserver.iis.security)