Re: standalone CA customized certificate
- From: Brian Komar [MVP] <bkomar@xxxxxxxxxxxxxxxxx>
- Date: Tue, 20 Mar 2007 20:55:03 -0400
More questions inmline...
In article <6B07D5F8-DB2E-4AD5-83AA-
2CE1D88F4E7B@xxxxxxxxxxxxx>,
SunilVirmani@xxxxxxxxxxxxxxxxxxxxxxxxx says...
Brain,
I am sorry because of my limited knowledge. Let me explain the architecture
of my software
My software is divided into 3 parts
Terminal Software - run on thin terminal
Management Server - run on windows 2003 server
VPC Software- run on virtual pc.
who wrote thie management server. This is the key to
whether your application would work. I know of no
management server software that does what you want with
certs today.
1.To connect to VPC , thin client has to run Terminal Software
2.Terminal Software has to pass serial number and processor type to Mgmt
Server.
3.Management Server will authenticate the information passed.
4.Once the mgmt server authenticates the client , it will send message to
VPC agent to open the RDP port.
This is not the way VPC would work. You would only be
connecting to the VPC agent using the RDP port? If you
are using htis, the only attribute of the certificate
that is looked at is the EKU attribute and it must have
the Client AUthentication OID. In addition, the RDP
client is hard coded to *only* look for smart card-based
client authentication certs, definitely not machine
certs....
Thus only thin terminal authenticated by the VPC is able to connect to the
virtual PC.
Now while passing serial number and processor type in step 2 , i want to
pass this information encrypted using the private key of machine certificate.
So now server can verify the information is sent by the right machine.
You are reinventing the wheel. The RDP connection can
use TLS to encrypt the information. You have the key
exchang backwards. When you connect to a server, you
validate the server certificate. The server certificate
is used to protect a symmetric key that is used to
encrypt any data. A client machine certificate is never
used to protect data. It is the responsibility of the
server cert.
Your architecture seems to be flawed. Look to standards,
Please let me know if you have any question.
rather than creating your own solution.
<snip>
.
- References:
- standalone CA customized certificate
- From: sunil
- Re: standalone CA customized certificate
- From: Brian Komar [MVP]
- Re: standalone CA customized certificate
- From: sunil
- Re: standalone CA customized certificate
- From: Brian Komar [MVP]
- Re: standalone CA customized certificate
- From: Brian Komar [MVP]
- Re: standalone CA customized certificate
- From: Sunil Virmani
- Re: standalone CA customized certificate
- From: Brian Komar [MVP]
- Re: standalone CA customized certificate
- From: Sunil Virmani
- standalone CA customized certificate
- Prev by Date: Re: standalone CA customized certificate
- Next by Date: Re: standalone CA customized certificate
- Previous by thread: Re: standalone CA customized certificate
- Next by thread: Re: standalone CA customized certificate
- Index(es):
Relevant Pages
|
|