Ecrypt LOB using SecureFile

Question

Dear all,
from whom the LOB encrypted file is protected? Suppose I create a table that contains an encrypted LOB and insert a value on it:
CREATE TABLE t1 ( a CLOB ENCRYPT IDENTIFIED BY foo)
LOB(a) STORE AS SECUREFILE (
CACHE
SQL> insert into t1 values ('dada');
1 row created.
SQL> commit;
Commit complete.when I try to access the table from the other schema that have a SELECT privilege on it, it isn't asked for any password. On the other hand, a schema that doesn't have the privilege, won't even able to get into the table since there is an insufficient privilege error.
Is there any condition where a user wants to access the table, he needs to enter password ("foo")?
best regards,
Val
Edited by: Valerie Debonair on Oct 6, 2011 11:30 PM

Answer 1

I think you'll find it's more to do with the underlying data at the operating system level. The datafiles can't just be taken and hacked into another database so that someone can create a similar table against that data and see it without knowing what password is required to decrypt the data.
It's expected that if you give select permission to another user on that table, then they should be able to select from it.