Re: I need root to be able to connect internal.

From: Rick Wessman <rwessman_at_rwessman.us.oracle.com>
Date: 1995/10/06
Message-ID: <RWESSMAN.95Oct6090242_at_rwessman.us.oracle.com>#1/1


The reason is the "connect internal" is allowed without a password if the connection is secure and the user is validated by the operating system. Because the SQL*Net V1 pipe driver exec's the Oracle server, the client's user name can be obtained securely from the operating system. For this reason, the protocol is deemed to be secure.

                                Rick
                                Rick Wessman
                                Network Management Products
                                rwessman_at_us.oracle.com

In article <453bkg$c4i_at_tbsnames.turner.com> phollard_at_bambam.turner.com (Pierre Hollard) writes:

>In article <44rc99$csj_at_nomad.urich.edu>,
>Michael Huneycutt <mhuney_at_sonic.urich.edu> wrote:
>>
>> Can someone help me with a problem I have. I have put root into the
>>dba group, but still am unable to connect internal when using sqldba. Is
>>there some sort of quirk in Oracle 7.1.6 that prevents root from doing a
>>connect internal even when root is in the dba group.
>
>Try to set the TWO_TASK variable to 'p:':
>
>TWO_TASK=p:; export TWO_TASK (in bourne shell)
>
>This should fix your problem (but don't ask me why!!!)
>
>--

-- 
                                Thanks,
                                Rick
                                Rick Wessman
                                Network Management Products
                                Server Techologies
                                Oracle Corporation
                                rwessman_at_us.oracle.com
Received on Fri Oct 06 1995 - 00:00:00 CET

Original text of this message