Database Reference
In-Depth Information
more-enduring functions and procedures in the next chapter. But because we are done here, let's clean
up after ourselves and remove these structures with the following commands as
appsec
user:
DROP PROCEDURE p_get_rsa_crypt_sysdate;
DROP FUNCTION f_get_rsa_crypt;
Chapter Review
Perhaps this was a lot of ground to cover in a few short pages, but there wasn't a lot of code required. I
think you'll agree that if this is all that's required to do Public Key Encryption, we should all be doing it!
Here is a list of PKE-related steps we took:
•
Created the public and private key set.
•
Got the modulus and exponent of the public key.
•
Re-created the public key from the modulus and exponent.
Generated an appropriate
Cipher.
•
Initialized the
Cipher
to do encryption or decryption using either the public or
private key.
•
•
Called the
Cipher.doFinal()
method to do both encryption and decryption.
In addition to the PKE aspects, we learned about the
Serializable
interface and about how we can
serialize objects to pass them around and store them.
We also established a standard form for calling Oracle procedures from an
OracleCallableStatement
that will allow us to exchange data and provide good error reporting back to the client, in a controlled
fashion to be handled by the application programmer.
We discussed
final
methods, Java constants,
static
methods,
private
constructors, and
static
initializers, with an aside on time zones.
All of this took place within our introductions to the
OracleJavaSecure
class that we will be building
and extending during the course of this topic.
