Hi All, The easiest way to protect the key is to create a package owned by the data owner and create functions within the package to encode and decode the data. Ensure the encryption key is defined in the package body.
Grant execute privileges to the data entry schemas. The view ALL_SOURCE will only show the package header and not the package body This will not protect against rogue DBA's or network sniffing HTH Dave -- Dave Morgan Operations Manager, Rigskills Canada Canada's Geographical Oilfield Services Locator http://www.rigskills.ca [EMAIL PROTECTED] 403 399 2442 -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Dave Morgan INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
