Database Reference
In-Depth Information
Message encryption
NSB supports the AES or Rijndael encryption algorithm. This is a symmetric key al-
gorithm, so both the program encrypting the data and decrypting the data must share a
secret key for their effort; see
http://en.wikipedia.org/wiki/Ad-
Encrypting data will depend on the needs of the organization, but common items could be
any passwords, financial information, or customer's personal identification information.
AES is the strongest symmetric encryption algorithm, and most languages, such as Java
and C#, provide API support to use it.
We know that part of the configuration on both sides will be a secret key.
In this section, we will be using the
Encryption
solution with the following projects:
•
Client
: The client will send encrypted credit card messages to the server.
•
Server
: The server will receive the credit card message and decrypt it.
•
Messages
: This refers to the message format that is being passed between the cli-
ent and the server.
Both the client and server must be running. The client will have a prompt to send messages
to the server:
Once you press
Enter
, you will see that the message is encrypted on the server queue: