Re: Oracle File Permission
Date: 1997/09/12
Message-ID: <3418a16d.24045339_at_news.us.oracle.com>#1/1
On Thu, 11 Sep 1997 00:37:38 +0700, Jim Forest <jlam_at_unocal.com> wrote:
>My UNIX system adm recently increase UNIX security level, and the
>system reports serveral red alert relating to file setting.
>Particularly, $ORACLE_HOME/bin/oracle and SQL*Net files.
>
>He ask why does file oracle set to 4755. I know Oracle requires this
>sticky bit, but I can find any documents, official documents, to satisfy
>his security obsession.
oracle userid owns the database files and should be the only userid that should have read/write permissions on the data. If your system admin is concerned about the security of the oracle architecture in any way have them check out the following web page regarding Oracle's security evaluations:
http://www.oracle.com/products/oracle7/server/whitepapers/compsecurity/html/chapter4.html
Hopefully that will convince them of the product's inherent security. Full report is available from NSA.
[Quoted] P.S. Am I wrong in thinking that we are really referring to the setuid bit which affects the effective userid of the process and the sticky bit is actually something to help certain processes stay memory resident?
>
>Please help.
>
>Thank you,
>Jim.
>
usual - my thoughts not necessarily reflecting opinions of my employer etc. disclaimer...
Dave Sidwell. Received on Fri Sep 12 1997 - 00:00:00 CEST
