Re: ODBC Drivers !!!!!!!!!!!
Posted in 1998
Topics: Stored Procedures & SPL, Connectivity: ODBC / JDBC / .NET, Connectivity: ESQL/C, 4GL & Embedded SQL, Server Administration, Security, Permissions & Auditing
I think this is the basic of DATABASE design:, granting an revoking connect, update ... rights at database level for the different users etc. etc. Without ODBC you'll have the same problems with DBACCESS ! Secure your database at database level. Regards Marco de Jong Nils Myklebust wrote: > Yes, this is one quote from that white paper. > First: It does explain ODBC in a better way than most other things I > have seen on the web. > Second: Here is another quote that is a little more central, although > also OpenLink related: > The key here to us and many others is security as it relates to access > control. > If you have followed previous long descussions here at c.d.i. (which > are hardly worth repeating) you know many people have found > significant problems with using ODBC at all. If a user have access to > one program that does direct updates to the database (even a 4GL or > ESQL/C program running on a Unix server) that user can use the login > name and password from that program when starting MS Access and get > the same rights to update any table in the database. Appart from > either using stored procedures exclusively for database updates or > some very limited protection via roles there is no way of protecting > against this with the Informix ODBC drivers.