Database Reference
In-Depth Information
At the bottom of Figure 6-1, we illustrate how the client calls methods to decrypt the secret
password key artifacts and to build an equivalent secret password key. The key image at the bottom
represents the secret password key on the client.
Figure 6-1. Key exchange
In Figure 6-2 you can see an illustration of the example processes for exchanging encrypted data
between the client and Oracle database. In the top one third of Figure 6-2, you see the process of doing
key exchange and encrypting data on the Oracle database. That encrypted data is returned to the client
in the OUT parameters of the p_get_des_crypt_test_data procedure. Here we refer to block [B] of Figure
6-1, where we saw the secret password key being built on Oracle database and returned to the client. In
Figure 6-2, in addition to building the secret password key, we use that key to encrypt data that is
returned to the client in encrypted form.
In the middle section of Figure 6-2, by a call to the getDecryptData() method (version A of two
methods with that name), we see an illustration of how the client decrypts data coming from Oracle
database. We outline this section of Figure 6-2 and label it as block [C] —it illustrates a standard process
for decrypting data. You can see that an equivalent secret password key, labeled DES, is built on the
client (as needed) during the decryption process.
The last section of Figure 6-2, at the bottom shows the mirror image of this process. In that
illustration, the client uses the equivalent secret password key that has already been built to encrypt
 
Search WWH ::




Custom Search