Need help on Oracle banner

[kimosabe]

Need help on how to create an Oracle banner when logging to Sqlplus for hackers.

The message that I want display is
"This system is being monitored...if you are log on illegally, log off now"...

If any one can help me, it will be very much appreciated. Thank you.

 

[vijaychin]

You should make change to the glogin.sql file location in the server's sqlplus directory.

 

[karluk]

I'm afraid Vijay's suggestion won't work. The average hacker is logging in from a remote location, and modifications to glogin only affect the local machine.

The only suggestion I can think of would be to write a logon trigger. Unfortunately a perusal of the documentation suggests that logon triggers can't modify this kind of interaction.

 

[vijaychin]

In Unix, if you keep a login.sql in the directory where you will run the sqlplus command, the contents of this file will be executed after the glogin.sql. I still think that, if you change the glogin.sql file, which is nothing but global, the script will be executed for every user who connects to the system.

Give it a shot.

 

[vijaychin]

TECHNET says
------------

Setting Up Your SQL*Plus Environment :

You may wish to set up your SQL*Plus environment in a particular way (such as showing the current time as part of the SQL*Plus command prompt) and then reuse those settings with each session. You can do this through a host operating system file called LOGIN with the file extension SQL (also called your User Profile). The exact name of this file is system dependent; see the Oracle installation and user's guide provided for your operating system for the precise name.

You can add any SQL commands, PL/SQL blocks, or SQL*Plus commands to this file; when you start SQL*Plus, it automatically searches for your LOGIN file (first in your local directory and then on a system-dependent path) and runs the commands it finds there. (You may also have a Site Profile, for example, GLOGIN.SQL which is run before LOGIN.SQL. See"Setting Up the Site Profile" for more information on the relationship of Site and User Profiles.)

 

[karluk]

I'm afraid I interpret this documentation as confirming that both login.sql and glogin.sql have to be on the client machine. It appears that the difference is that login.sql is specific to a user, whereas glogin.sql is executed by everyone who connects from that client.

Nevertheless, as you say, if in doubt give it a test.

By the way, the documentation does indicate that users of SQL*Plus worksheet in Enterprise Manager do, indeed, run the glogin.sql that resides on the server. That's because the SQL*Plus worksheet executable is started on the server, not the client. Of course this won't help - you can't force hackers to connect in only a specific way.