RE: lsnrctl passwords
Date: Wed, 16 Apr 2008 13:43:06 -0500
I have seen examples of the second problem. On one of my projects our UNIX sysadmin people had a habbit of trying to save on system installation times by copying the Oracle directory tree to the new server. I had scripts in place which automatically stopped and started the listener when the system rebooted. When the UNIX people bounced the new server, it would shut down the listener on the server that they copied from. Having said that, I am not sure how a password on the listener would prevent this since my shutdown script contained the encrypted password for the listener.
- Peter Schauss
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Niall Litchfield Sent: Tuesday, April 15, 2008 7:53 AM
To: jkstill_at_gmail.com; William.Blanchard_at_kohler.com; oracle-l_at_freelists.org
Subject: Re: lsnrctl passwords
Not entirely sure that I buy the second example but the first is definitely your major concern. Insiders are nearly always the problem
On 14/04/2008, Jared Still <jkstill_at_gmail.com> wrote:
> On Fri, Apr 11, 2008 at 9:00 AM, Blanchard William <
> William.Blanchard_at_kohler.com> wrote:
> > Wouldn't they need access to your network in order to access the
> > listener? I know that you can set up a similar entry in a
> > listener.ora and remotely access the listener (I did this to prove
> > it) but I was behind the firewall. I tried from home but wasn't able
> > to access the listener using
> > same technique.
> Malicious users can exist inside the network.
> AKA employees
> This can also happen accidentally, say a DBA copies a listener.ora to
> his PC for modification, forgets to modify it, then stops the
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
-- Niall Litchfield Oracle DBA http://www.orawin.info -- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Wed Apr 16 2008 - 13:43:06 CDT