Re: Stop use ODBC

I'd like to know what the layout is, too. Is it ODBC per se that is the problem, or SQL*NET/Net 8 client/server connections in general, or what? ODBC connections ultimately end up as SQL*NET connections, it's just another layer.

What we did to prevent any ad hoc naughtiness was just create users with no privileges except connect, and created one or more roles for each application with the necessary privileges, passworded the roles, and had the apps internally set to the role and supply the password to do it; Ken Jacobs and I had a long talk about this years ago and he had a slightly more elegant approach (well what would you expect?) that I can't now recall. But this worked fine for us, and guarded against not only the dread desktop access via ad hoc stuff, but people getting into UNIX and using SQL*PLUS (which was not nearly as likely, as end-users but for a few never even had UNIX logins.)

Roles were probably one of the greatest things to come along in Oracle, to manage object and privilege access without driving the DBA insane.

RSH.. "Paul Brewer" <paul_at_paul.brewers.org.uk> wrote in message news:3c76ae72_1_at_mk-nntp-1.news.uk.worldonline.com...
> Can you please describe what gaping holes exist in your Oracle
> security, which mean that application users must be prevented from
> connecting to the database in any other way than via the application?
>
> Group, Jonathan,
> Can we get this onto the FAQ list,
> if it isn't already?
>
> Paul
>
> "France" <fbi2_at_videontron.ca> wrote in message
> news:sdgd8.4707$p31.230007_at_wagner.videotron.net...
> > How build a procedure, a routine, I want to kill session when anyone
> > connect with ODBC.
> > It's possible kill a connection ODBC in Oracle8i?
> > I want restrict the access at database and to implanted a security .
Only
> > one application access at database ansd this application don't use a
ODBC
> > connection.
> >
> >
> > Please I need your help
> > --
> > France
> >
> >
>
>
Received on Sat Feb 23 2002 - 12:33:28 CST