RE: methodology to keep only certain programs to connect to

You can't.

This is one of the reasons I haven't tried to use this.

Jared

Kevin Lange <kgel_at_ppoone.com>
Sent by: root_at_fatcity.com
 09/10/2002 10:53 AM
 Please respond to ORACLE-L  

        To:     Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
        cc: 
        Subject:        RE: methodology to keep only certain programs to connect to

With a setup like this, how do you stop a user from simply renaming the program they are using to match what you expect to see and, therefore, getting past your security ??
-----Original Message-----

From: Shaw John-P55297 [mailto:john.shaw_at_motorola.com] Sent: Tuesday, September 10, 2002 11:59 AM To: Multiple recipients of list ORACLE-L Subject: RE: methodology to keep only certain programs to connect to

use v_$mystat - it has the sid - then do your join with v$session
-----Original Message-----

From: JOE TESTA [mailto:JTESTA_at_longaberger.com] Sent: Tuesday, September 10, 2002 10:58 AM To: Multiple recipients of list ORACLE-L Subject: methodology to keep only certain programs to connect to

I've been tasked to ensure only certain app programs access the database.  

I'm thinking on-logon trigger, check the program field from v$session. unfortunately v$session is for all sessions, i can't seem to find the view that tells me only MY info during login. I only want the sid, serial#, username and program for my just now connection to the database.  

Does this exist or am I going about this the wrong way?  

We're thinking of checking those fields to make sure sql*plus, toad, etc can't connect as a particular user(even though the password is known out in the community).  

any ideas would be greatly appreciated. Received on Tue Sep 10 2002 - 14:01:51 CDT