|
Key Databases
Each CSP has a key database in which it stores its persistent cryptographic
keys. Each key database contains one or more key containers, each of which contain all the key pairs belonging to a specific user (or
CryptoAPI client). Each key container is given a unique name, which applications
provide to the CryptAcquireContext function when acquiring a handle to the key container. Following is an
illustration of the contents of a key database:
The CSP stores each key container from session to session, including all the
public/private key pairs it contains. However, session keys are not preserved
from session to session.
Generally, a default key container is created for each user. This key
container takes the user's logon name as its own name which is then used by any number
of applications. It is also possible for an application to create its own key
container (and key pairs) which it usually names after itself.
Related Links
Software for Delphi and C++ Builder developers
Software for Visual Studio .NET developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET
TMS Scripter Studio Pro components for Delphi/C++Builder
More Online Helps
Win32 Multimedia Programmer's Reference (mmedia.hlp)
OLE Programmer's Reference (ole.hlp)
Microsoft Windows Pen API Programmer's Reference (penapi.hlp)
Microsoft Windows Sockets 2 Reference (sock2.hlp)
Microsoft Windows Telephony API (TAPI) Programmer's Reference (tapi.hlp)
Unix Manual Pages
|
