By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,021 Members | 912 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,021 IT Pros & Developers. It's quick & easy.

DB2 UDB V9.5 Windows ENCRYPT

P: n/a
It seems that I must pass a "SET ENCRYPTION PASSWORD =" to each stored
procedure that puts an encrypted value into a column. Also seems that
I don't have to specify that password when using DECRYPT_CHAR().

Does that mean that a different password can be used for each entry
into that column and the dbm stores it someplace?

This is important because it gives my app a chance to generate random
passwords and not have to remember them.

SS
Nov 16 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
28******@gmail.com wrote:
It seems that I must pass a "SET ENCRYPTION PASSWORD =" to each stored
procedure that puts an encrypted value into a column. Also seems that
I don't have to specify that password when using DECRYPT_CHAR().

Does that mean that a different password can be used for each entry
into that column and the dbm stores it someplace?

This is important because it gives my app a chance to generate random
passwords and not have to remember them.
ENCRYPT/DECRYPT is meant for the user and not the system. So yes, each
row and each column can have a different password and it is the users
responsibility to know it. DB2 does NOT store the password. It does
store the "hint" (if provided).

Of course no-one prevents the system from using the feature itself for
its own purposes.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Nov 16 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.