|
Storing Session Keys
This section discusses how you use CryptoAPI to store a session key for later
use. This is useful in those situations where you have encrypted a file using a
key and want to decrypt the file at a later time. Another possible situation
is one in which you have shared the session key with another user and you want
to use the key at a later time to send the other user encrypted messages.
In either case, your application will have to store the session key outside of
the CSP for a certain period. Following is the procedure for storing a session
key.
- Create a simple key blob using the CryptExportKey function. This will transfer the session key from the CSP to your
application's memory space. Specify that your own key exchange public key be used to
encrypt the key blob.
- Store the signed key blob to disk. The assumption is made here that all disks
are nonsecure.
- Later, when you need to use the key, read the key blob from disk.
- Import the key blob back into the CSP using the CryptImportKey function.
If the session key is just to be bundled with an encrypted file (so that you
can later decrypt the file), and the key is not going to be used to encrypt any
more data, then the above procedure provides adequate security.
If you plan to use the session key for encryption at a later time, then the
key blob should be signed with your key exchange key before the key is stored to
disk. When you later read the key blob back from disk, you should validate the
signature to make sure the key blob is intact. If these steps are omitted, then
someone with access to your storage media can create their own session key,
encrypt it with your key exchange public key, and substitute it for your key
blob. You could then unknowingly use their session key to encrypt files and
messages, which the unscrupulous user could then easily decrypt. (Digital signatures
are discussed in detail in the section Hashes and Digital Signatures.)
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|