|
Posted by Joe Kaplan on September 28, 2006, 2:31 pm
Please log in for more thread options 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
--
> westes-usc@noemail.nospam 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
| 
XML Sitemap