Hi Michal,
It's a security breach and bug #2366907
has been opened for that.
So protect carefully your listener.ora file from non privileged
readers.
Regards
At 01:53 08/10/2002 -0800, you wrote:
Yes, you can change your listener.ora file permission up to 600 on the
server side. In a shell
Yes, you can change your listener.ora file permission up to 600 on the
server side. In a shell script you can then use encrypted password found
in listener.ora on line PASSWORDS_listener.
lsnrctl EOF
set password C6C144CF750E3CA5
stop
exit
EOF
If the password is not in the listener.ora file,
Hi ,
We can very well protect the Server side executables by changing the
permission of the
file . We had implemented this on all our database sites and normal
user don't have access
to lsnrctl,svrmgrl,namesctl etc .You can also protect the
listener.ora file by changing
