Re: DB link Secureness

From: Lok P <loknath.73_at_gmail.com>
Date: Sat, 19 Dec 2020 00:02:39 +0530
Message-ID: <CAKna9VadXjgkWPCec481_sW1y6U20KpzEkWDr3W+CNmqnXH0Hg_at_mail.gmail.com>



I checked two ways i.e first by taking the export dump and doing impdp with parameter SQLFILE and as I see in version 11.2.0.4 the dblink DDL is having a bind variable in place of password.

Then I did try to see the .DMP file content and it's all junk. I didn't see any hashed value or bind value. So that looks perfect with respect to security stand point.

Now one thing wanted to see, if somebody takes the export dump of dblink from PRODDB and import it in some Dev database say DEVDB , will that dblink will be created without any error? And in that case will the user silently able to connect to the REMOTEPROD using that dblink without anyone's notice? If it's true then even the password is not exposed to outside but still it's a security risk. Correct me if wrong?

On Thu, 17 Dec 2020, 9:59 am Lok P, <loknath.73_at_gmail.com> wrote:

> I am not very sure how to create DB links using TCPs and if it's the
> safest with no security loophole. Can you explain a bit and we are on
> 11.2.0.4 so if there is any version dependency?
>
> But the below doc does state that the password was stored as cleartxt in
> sys.link$ in prior 10GR2. But nothing mentioned if export/import password
> is exposing that in clear text in current versions or not?
>
> MOS Doc ID 202987.1
>
> On Thu, Dec 17, 2020 at 8:14 AM Mladen Gogala <gogala.mladen_at_gmail.com>
> wrote:
>
>> Or create link using TCPS.
>>
>> On 12/16/20 2:03 PM, Powell, Mark wrote:
>> > Ask the security team to present you proof the password can be exposed
>> > when some exports/imports the link
>>
>> --
>> Mladen Gogala
>> Database Consultant
>> http://mgogala.byethost5.com
>>
>> --
>> http://www.freelists.org/webpage/oracle-l
>>
>>
>>

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Dec 18 2020 - 19:32:39 CET

Original text of this message