Re: Re[2]: ODBC with informix

<< We admininster a package wherein the end user requires all permissions on all tables in order to be able to carry out their normal job function. That's an invitation to disaster. What kind of application requires that all users have access to all tables? Whenever I've seen that scenario, it is usually because - someone doesn't understand SQL or the concept of database security or - hasn't done sufficient analysis to determine which users and groups need which permissions. Glyn, it sounds like the package developer needs some feedback that its security model is wanting... ==================== Ken North =========================== http://ourworld.compuserve.com/homepages/Ken_North e-mail: KenNorth@msn.com kennorth@interserv.com 71301.1306@compuserve.com Ken North Computing 2604B El Camino Real, #351 Carlsbad, CA 92008-1214 FAX: 760-729-5127 ========================================================== david.ashby@workcover.nsw.gov.au wrote in article <6f6s7e$cmp$1@news.xmission.com>... > > Matt Reprogle wrote : > > > Jay Hannah wrote: > > > > Killspamrs wrote: > > Agreed. We admininster a package wherein the end user requires all > permissions on all tables in order to be able to carry out their > normal job function. However, we also need to give ODBC access to > certain individuals to enable database access via MSOffice, for > example. Therein lies our quandary. Since the user has a pukka (UNIX) > login to the database with full permissions, how do we prevent him/her > attaching via ODBC as the same user and thereby open the flood gates ? > > Glyn Balmer > I.T. Consultant > BICC Cables Limited > Erith Kent UK