Oracle A423961 Manual Do Utilizador
☞
4 – 6
Oracle7 Server Getting Started for Windows NT
found, the user is granted or denied privileged access to the
database
database
•
REMOTE_LOGIN_PASSWORDFILE=SHARED:
The SHARED value of this parameter affords backward
compatibility with earlier releases of Oracle7. Oracle7 looks for
the same files as it does when the value is EXCLUSIVE, but only
the INTERNAL account is available for privileged access. Users
will not be able to log in with SYSOPER or SYSDBA privileges
even if those privileges are granted in the password file.
The SHARED value of this parameter affords backward
compatibility with earlier releases of Oracle7. Oracle7 looks for
the same files as it does when the value is EXCLUSIVE, but only
the INTERNAL account is available for privileged access. Users
will not be able to log in with SYSOPER or SYSDBA privileges
even if those privileges are granted in the password file.
•
REMOTE_LOGIN_PASSWORDFILE=NONE:
If the value of this parameter is NONE, either one of the first two
security conditions above is true, or no users are granted access to
the database.
If the value of this parameter is NONE, either one of the first two
security conditions above is true, or no users are granted access to
the database.
Additional Information:
See Initialization Parameter Files in this
Guide for details on Windows NT initialization parameters.
Database Password Encryption
With this release of Oracle7 Server for Windows NT, you can require
that the password used to verify a remote connection—that is, a
connection over SQL*Net—always be encrypted. You do this in two
steps:
that the password used to verify a remote connection—that is, a
connection over SQL*Net—always be encrypted. You do this in two
steps:
•
Set the DBLINK_ENCRYPT_LOGIN initialization parameter on
the server to TRUE.
the server to TRUE.
•
Set the ORA_ENCRYPT_LOGIN environment variable on the
client machine to TRUE.
client machine to TRUE.
Once these parameters are set, whenever you attempt a remote login,
Oracle encrypts the password before sending it to the remote database.
If the connection fails, the failure is noted in the audit log. Oracle then
checks the appropriate parameter values. If either is set to FALSE,
Oracle attempts the connection again using an unencrypted version of
the password. If the connection is successful, the success is noted in the
audit log, and the connection proceeds.
Oracle encrypts the password before sending it to the remote database.
If the connection fails, the failure is noted in the audit log. Oracle then
checks the appropriate parameter values. If either is set to FALSE,
Oracle attempts the connection again using an unencrypted version of
the password. If the connection is successful, the success is noted in the
audit log, and the connection proceeds.
Attention:
Releases of the Oracle7 Server prior to 7.1 did not
support encrypted passwords. Therefore, if you know you are
connecting to earlier versions of an Oracle7 Server for Windows
NT, you must set the initialization parameter
DBLINK_ENCRYPT_LOGIN to FALSE for the connection to
succeed.
connecting to earlier versions of an Oracle7 Server for Windows
NT, you must set the initialization parameter
DBLINK_ENCRYPT_LOGIN to FALSE for the connection to
succeed.