Re: access security

Path: emory!ogicse!usenet.coe.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!mips!jrg From: jrg@mips.com (John Galloway) Newsgroups: comp.databases.informix Message-ID: <ksieffINN33s@spim.mips.com> Date: 20 Mar 92 01:03:43 GMT References: <564@gsiserv.UUCP> Organization: Galloway Research Posted: Thu Mar 19 17:03:43 1992 NNTP-Posting-Host: moosehead.mips.com In article <564@gsiserv.UUCP> sopena@gsi.fr (Christophe Sopena) writes: > >We use ESQLC 4.0 with Informix ON-LINE 4.10 on a Sparc station 2. >In a normal use, the users will access the database, only through applications >we are developping. >Is it possible to deny access to a user trying access the database in any other way? The two other points of possible entry are accessing the chunks (the files that make up the database space) which will either be raw devices or cooked files. The mode OnLine expects is 660 informix informix (actaully the user might be adjustable with only the group needing to be informix). The shared memory is created with the same mode. So the normal access control on Sun is enforce here. If folks have access to the database space files (are in the informix group, or have super user or ...) then they will be able to access (and screw up) things accordingly. The same goes for shared memory, if a user (like root) can attach and read it directly then they can get to any block that a legit users has recently accessed. -jrg -- internet jrg@galloway.sj.ca.us John R. Galloway, Jr 795 Beaver Creek Way applelink D3413 CEO...receptionist San Jose, CA 95133 Galloway Research (408) 259-2490