|
Posted by Brian Komar \(MVP\) on February 28, 2008, 1:21 pm
Please log in for more thread options Your understanding of how SSL works is very flawed.
The SSL certificate for RDP is a *server-side* certificate (like *all* SSL
applications)
GIving the certificate to users is a complete and utter waste of time.
Please see RFC 4346 for details on how SSL works.
What you are trying to do with certificate will *never* work, no matter
whether you get the certificates from a commercial or private CA
Brian
>I want to secure it to limited users/computers. I wanted to create a SSL
> certificate and only be able to manually pass out that certificate.
>
> With Microsoft CA certificate, it didnt limit the user/computers.
>
> Sam
>
> "Brian Komar (MVP)" wrote:
>
>> How would a 3rd party cert solve your problem. The certificate encrypts
>> the
>> connection, it does not limit logons no matter whether the cert is issued
>> by
>> a private CA or a commercial CA
>> Brian
>>
>> > How do I add a thrid party SSL certicate to remote desktop?
>> >
>> > I read all the documentation I can find about SSL and Remote Desktop
>> > and
>> > the
>> > ones I find want me to use Microsoft CA Services. I tried that, however
>> > it
>> > doesn't force only certain system to login. Any systems can login. Even
>> > though I can create a SSL Remote Desktop connection.
>> >
>> > I think it would be better if I went with a third party certifacte.
>> >
>> > Thanks,
>> >
>> > Sam
>>
>>
| 
XML Sitemap