|
|||||||||
|
|||||||||
|
|||||||||
 |
|||||||||
| |
||
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
ASP Free Forums Sponsor:
|
|
|
|
#1
July 24th, 2007, 03:17 AM
|
|||
|
|||
|
Commercial public key infrastructures (PKI)
What are commercial public key infrastructures (PKI), and why would you recommend using one rather than implementing such a capability in-house with the
software developers you may already have? Thanks. 
|
|
#2
July 29th, 2007, 01:30 PM
|
||||
|
||||
|
A PKI is a certificate storage facility that provides a hierarchical trust structure along with certificate management functionality, like having the power to issue, revoke, store, retrieve and trust certificates. The primary feature of PKI is the Certificate Authority (CA) who is responsible for issuing certificates to authorized users.
Why would you use this rather than in-house? It's based on the level of trust. For example, people trust that Verisign will issue a certificate to a person only after they have done their homework on the person's true identity. If they didn't always do their homework, they would lose marketshare as people would trust them much less. In your situation, it all depends on how you plan to use these certificates.
__________________
jmurrayhead Did I help you out? Make me popular by clicking the  icon!New Members:Proper way to post a question Powered by ASP.Net
|
|
| Viewing: ASP Free Forums > System Administration > Windows Security > Commercial public key infrastructures (PKI) |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
|
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
