Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Blocking 'Some' applications

Re: Blocking 'Some' applications

From: Billy Verreynne <vslabs_at_onwe.co.za>
Date: 1997/11/18
Message-ID: <01bcf41d$9aa89660$f3040059@billyv.vslabs.co.za>#1/1

JBringolf <jbringolf_at_uncfsu.campus.mci.net> wrote in article <3470FCFA.20C2F11E_at_uncfsu.campus.mci.net>...
> Trying to find out if anyone has looked into the possibilities which
> would allow the Database to allow connections from specific clients and
> block connections from others. Example: Allow an individual access to
> shared database tables using a company supplied program but not allow
> him/her to connect if they try using the same UserID/Password in
> MSAccess.
>
> Any ideas...

Monitor column PROGRAM in V$SESSION via a cron job or something and kill any sessions that has an "illegal" program entry. Alternatively built a DBMS_APPLICATION_INFO.SET_CLIENT_INFO call into the client application and kill any user session from V$SESSION where CLIENT_INFO contains "invalid" data.

Better still, use a baseball bat on any PC that has M$-crapaccess loaded (and don't forget the user!)... :-)

regards,
Billy Received on Tue Nov 18 1997 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US