Oracle Advanced Security
Release 8.1.7

*******************************************

Copyright (C) 1998, 1999, 2000 Oracle Corporation

This software/documentation contains proprietary information of Oracle
Corporation; it is provided under a license agreement containing
restrictions on use and disclosure and is also protected by copyright
law.  Reverse engineering of the software is prohibited.

If this software/documentation is delivered to a U.S. Government
Agency on the Department of Defense, then it is delivered with
Restricted Rights and the following legend is applicable:

RESTRICTED RIGHTS LEGEND:

Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of DFARS
252.227-7013, Rights in Technical Data and Computer Software (October
1988).

If this software/documentation is delivered to a U.S. Government
Agency the Department of Defense, then it is delivered with
"Restricted Rights," as defined in FAR 52.227-14, Rights in Data -
General, including Alternate III (June 1987).

Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

This product contains encryption and/or authentication engines from
RSA Data Security, Inc. Copyright 1996 RSA Data Security, Inc.  All
rights reserved.

Oracle and SQL*Net are registered trademarks of Oracle Corporation,
Redwood City, California.  Net8, Oracle8 and Oracle8i are trademarks
of Oracle Corporation, Redwood City, California.  All other products
or company names are used for identification purposes only, and may be
trademarks of their respective owners.


*********************************************


OVERVIEW
--------

Oracle Advanced Security release 8.1.7 bundles security services for 
Oracle8i.  It secures connections over all protocols into Oracle8i and 
integrates a Public Key Infrastructure (PKI).  Oracle Advanced Security 
provides data encryption and integrity for all network protocols into 
the database, including Net8 with native encryption, Net8/SSL, IIOP/SSL, 
and Java-based encryption for Thin JDBC clients.  It integrates with 
third-party authentication, authorization and single sign-on services.  
It supports public-key solutions including Secure Sockets Layer (SSL) 
and X.509 Version 3 certificates (provided by third party certificate 
servers) and bundles related tools, Oracle Wallet Manager 2.1 and Oracle 
Enterprise Login Assistant 1.1.  It also enables SSL-based single sign-
on and enables certificate-based server-to-server authentication and 
database links. Oracle Advanced Security integrates with Entrust PKI in 
this release.

Oracle Advanced Security utilizes LDAP v3-compliant directory servers to 
centralize user management, and it bundles Oracle Enterprise Security 
Manager 2.0 to manage enterprise users and enterprise roles.  Oracle 
Advanced Security provides restricted use of Oracle Internet Directory 
release 2.1.1 for storing users and authorizations.  It also integrates 
with Microsoft Active Directory for role management.  

In this release, Oracle Advanced Security installs automatically
during Typical Install.  In order to use it, you must purchase
appropriate licenses, install it either automatically in Typical Install
or manually using Custom Install, then configure it on the servers 
and clients.  All components install in Typical Install except
CyberSafe, DCE, and Entrust (on the server) and the enterprise user
security features (on the client), which install in Custom Install.  
Although installed by default, Oracle Advanced Security is an extra cost
item and must be purchased when used.  This licensing requirement also
affects customers wishing to use security features in combination with
Java Beans (EJB over IIOP/SSL) or Database Enterprise Users (Net8/SSL).  
The exclusive exception is an HTTPS (HTTP/SSL) connection to the RDBMS
which does not require an Oracle Advanced Security license.


CHANGES IN THIS RELEASE
-----------------------

New in this release:
o Single internationally-available version with strong encryption
o 3DES and RSA RC4_256 support for native Net8 
o SHA-1 support for native Net8 
o Order of encryption algorithms in Net8 Assistant
o Strong encryption for Thin JDBC clients
o Entrust integration 
o Enterprise user management and single sign-on improvements

This release contains one internationally-available version of Oracle
Advanced Security containing strong encryption.  Previous versions
shipped as Domestic Edition or Export Edition.  The single version
provides strong encryption with up to 256-bit RC4 and 3DES encryption
for native Net8 and 3DES in SSL.  Note that customers using pre-8.1.7
versions can upgrade to the Domestic Edition of the version they are
running.


DATA ENCRYPTION AND INTEGRITY
-----------------------------

In this release, Oracle Advanced Security encrypts native Net8 with 
RSA RC4 with 256-, 128-, 56- and 40-bit keys, DES and DES40, and 
three-key (168-bit) or two-key (112-bit) Triple-DES.  It also provides 
data integrity checking with MD5 and SHA-1 algorithms for Net8.

When configuring Oracle Advanced Security encryption and integrity, 
choose the algorithms and key lengths in your preferred order.  
Negotiation is based on the left-to-right order in sqlnet.ora and top-
to-bottom in Net8 Assistant. 

Oracle Advanced Security release 8.1.6 successfully completed FIPS 
(Federal Information Processing Standard) 140-1 Level 2 validation of 
its native Net8 encryption components.  See Appendix D in the Oracle 
Advanced Security Administrator's Guide for required FIPS 140-1 
configuration parameters.  Users who intend to use Oracle Advanced 
Security in the FIPS 140-1 Level 2 validated configuration must apply 
tamper evident seals to the cover of each machine such that removal of 
the cover is detectable.

Oracle Advanced Security encrypts Thin JDBC client connections to the 
RDBMS with RSA RC4 256-, 128-, 56- and 40-bit keys, DES and DES40.  It 
also provides data integrity checking with MD5. 

Oracle Advanced Security SSL feature supports cipher suites with 
Triple-DES, RSA RC4 128-, 56- and 40-bit keys, DES and DES40.  The MD5 
and SHA-1 algorithms are included in the SSL cipher suites.


EXTERNAL AUTHENTICATION AND SINGLE SIGN-ON 
-------------------------------------------

Oracle Advanced Security supports RADIUS-compliant servers and
authentication devices.  To use the Java-based client interface for
RADIUS, you must set the LD_LIBRARY_PATH to 
$ORACLE_HOME/JRE/lib/sparc/native_threads.  To use RADIUS, you must
use native threads.  Set the variable THREADS_FLAG to "native" within
the Java Runtime Environment. 

In this release the RSA ACE/Server and tokens can authenticate Oracle 
users through the RADIUS adapter as well as the SecurID adapter.  Using 
the RADIUS plug-in to the ACE/Server, the ACE/Server acts as the RADIUS 
server and authentication server.  This is the final release in which 
Oracle Advanced Security supports both modes, in favor of RADIUS 
integration with the ACE/Server.  Functionality will remain the same.  

In this release, Oracle Advanced Security supports Kerberos V5 Release
1.0 authentication in its default configuration mode (currently, only
"des-cbc-crc" encryption mode is supported).  Kerberos V5 Release 1.0
can be obtained from Massachusetts Institute of Technology (MIT) web
site http://web.mit.edu/kerberos/www.  In this release, Oracle
Advanced Security supports MIT's new Kerberos configuration file
format.

In this release, Oracle Advanced Security supports Transarc's DCE/DFS
2.0 on Solaris 2.6.  In order to use DCE, you must install DCE
integration in Custom Install.  

This release of Oracle Advanced Security supports CyberSafe
TrustBroker Client Suite v1.2.  In order to use CyberSafe with Oracle
Advanced Security, you must install CyberSafe support in Custom
Install.  To use the products together, you must install CyberSafe GSS
Runtime Library v1.1 during the CyberSafe install.

This is the final release in which Oracle Advanced Security supports the 
Identix adapter, in favor of RADIUS support for biometrics. 

In order to require external authentication and disable username/
password authentication, set the sqlnet.ora parameter
SQLNET.AUTHENTICATION_REQUIRED=TRUE.  The default is false.


ENTRUST SUPPORT
----------------------

To configure the Entrust-ready version of the Net8 SSL adapter, it is
first necessary to have EntrustIPSEC Negotiator Toolkit Version 5.0
installed on all of the computers on which the Oracle clients and
servers are to run.  

WARNING: Entrust Integration support configures the Net8 SSL Adapter,
         to work with Entrust profiles only. If you have an
         Oracle Installation configured to work with Oracle Wallets,
         please do not install Entrust Integration feature.


PUBLIC KEY INFRASTRUCTURE
--------------------------

This release contains support for the Secure Sockets Layer (SSL)
protocol which secures networks with Public Key Infrastructure (PKI).
Use of the SSL protocol allows Oracle processes to authenticate one
another with X.509 Version 3 certificates.  SSL provides encryption
and data integrity with cipher suites, which are sets of
authentication, encryption and data integrity types.  In addition to 
using X.509v3 certificates for RSA asymmetric key authentication, SSL
provides Diffie-Hellman Anonymous cipher suites for non-certificate
based negotiation.

Oracle Wallet Manager creates wallets, issues certificate requests,
and manages public-key credentials.  To launch Oracle Wallet Manager,
you must run $ORACLE_HOME/bin/owm.  Oracle Wallet Manager looks for a
default wallet directory to create or open a wallet.  For example, in
Solaris, Oracle Wallet Manager looks in /etc/ORACLE/WALLETS/<user-id>.
The default directory should be created by the administrator who has
sufficient system privileges.  For security reasons, the user-id
directory must be accessible only to the respective user.

Enterprise Login Assistant can be launched by running
$ORACLE_HOME/bin/elogin.  This tool also requires the default wallet
directory for login.


ENCRYPTION AND AUTHENTICATION
Known Bugs and Workarounds
---------------------------

In this release, the NS features of Multiplexing and Connection
Pooling do not work if SSL transport is being used.

For the Identix adapter, if the fingerprint database is a Windows NT
server, set the sqlnet.ora parameter (for fingerprint database server)
to read: SQLNET.AUTHENTICATION_SERVICES=(NTS,NONE)

There is a known problem in which Oracle Clients (sqlplus or svrmgrl)
fail when the Radius Adapter is configured for CHAP
(challenge-response) mode.  To workaround this problem set
LD_LIBRARY_PATH environment variable to include
$ORACLE_HOME/JRE/lib/sparc/native_threads.


SECURE SOCKETS LAYER
Known Bugs and Workarounds
--------------------------

For the SSL adapter, dynamic specification of sqlnet.ora parameters such
as SSL_VERSION, SSL_CIPHER_SUITES and SSL_CLIENT_AUTHENTICATION, as
part of TNS Aliases, will not have any effect on the redirected
connections made to the database server.


ORACLE WALLET MANAGER
Known Bugs and Workarounds
--------------------------

The Oracle Wallet Manager splash screen does not show the proper font.
The workaround is to modify the $JREHOME/lib/font.properties to
include an alias of SansSerif.alias.helvetica=sansserif. (1093958)

Non-English versions of Oracle Wallet tools show help in English only.
The workaround is to edit the Wallet tool script (owm on unix and
owm.cl on NT) to add the appropriate language help file directory at
the beginning of the classpath.  This is also true for the Enterprise
Login Assistant. (1098469)

Certificate Request Creation fails with some multibyte character
sets. (1077099)

Oracle Wallet Manager's Online Help becomes unresponsive when modal
dialog boxes, such as the one to enter Certificate Request
Information, pop up.  The Online Help becomes responsive once the
modal dialog box is closed. (1114710)


ORACLE ENTERPRISE SECURITY MANAGER 2.0 
Known Bugs and Workarounds
-------------------------------

Attempting to place a database into an Enterprise Domain when it is
already a member of another Enterprise Domain results in a "General
Net8 LDAP Error."  In this release, ESM will refuse to add a database
to multiple Enterprise Domains.  After receiving this error message,
you must exit and re-enter the Databases Property Page of the
Enterprise Domain before adding or removing more databases to the
Enterprise Domain. (1064954)

When you remove a database from an Enterprise Domain, Enterprise Roles
within the Enterprise Domain may still contain Global Roles for that
database. (736159)

If you attempt to create a new object in the directory and the
operation fails (e.g., attempting to create an Enterprise User with an
invalid Base DN), ESM reports an appropriate error message.  However,
if you continue to use the same Create Object dialog to create the
object again, the dialog will quit without creating the object.  You
must invoke the Create Object dialog again in order to retry the
operation. (1041890)

When entering a new Database Schema Mapping entry for an Enterprise
Domain using the Enterprise Domain "Database Schema Mapping" property
page, ESM does not automatically provide a new row in the Schema
Assignments grid for entering the next Database Schema Mapping entry.
You must exit and re-enter the Property Page in order to obtain a new
row. (1019924)

When using the Browse Directory dialog, ESM selects an initial value
for the Directory Naming Context under which to search for objects in
the directory server.  If your directory server does not have any
Naming Contexts configured, ESM will revert to a most commonly found
top-level directory entry of "dc=com" as its default value.  If your
directory does not support "dc=com" then searches will fail unless you
manually enter a proper Directory Naming Context. (1098590)

Users in the 'netadmins' group have sufficient access privileges to
allow them to add mapping objects under the database objects, even
though this is typically a job of the database administrators.


Java SSL
Known Bugs and Workarounds
--------------------------

LDAP/SSL CONNECTIONS USING JNDI AND JDK 1.2 RESULT IN A CORE DUMP. The 
bug is that Java SSL is not thread safe when multiple threads share the 
same SSL connection. The workaround is that application needs to 
synchronize reads and writes when multiple threads do reads and writes 
concurrently on the same SSL connection. (1328188)


INSTALLATION
------------

During Oracle Advanced Security installation, three .bak files are
created: naeet.o.bak, naect.o.bak, and naedhs.o.bak.  They are located
in $ORACLE_HOME/lib.  These files should not be deleted because they
are required when executables are relinked during the de-installation
of Oracle Advanced Security.

If using Oracle Advanced Security on a "client only" machine (that is,
with no database present), it is mandatory to set the TWO_TASK
environment variable before starting the installation.  The TWO_TASK
variable points to an alias representing the database on a server
machine.  Setting the TWO_TASK environment variable enables Oracle
Advanced Security to be installed in "Client Only" mode.  See the
Oracle8i Administrator's Guide for more details on the TWO_TASK
environment variable.


ENHANCEMENTS TO PROBLEMS IN PREVIOUS RELEASES 
---------------------------------------------

Thin JDBC clients can connect securely with up to 256-bit RC4 and 56-bit 
DES encryption. 

As there is now one edition of Oracle Advanced Security with all 
encryption algorithms, any problems relating to encryption or cipher 
suites in Export and Domestic Editions have been resolved.

The problem has been fixed in which the Net8 layer could not propagate 
the SQLNET configuration parameter information to redirect connections 
(1113580).  It no longer effects Identix or SSL support. 

The bug has been fixed in which you could not start a second DCE
listener on the same node. (834788)

Anonymous database links now work with Kerberos authentication. (863864)

The bug has been fixed in which you could not simultaneously set the
TWO_TASK environment variable and use remote OS authentication. 
(1139334)
 
The problem has been fixed in which the database could not register
MTS Dispatchers with a listener over SSL.  MTS Dispatcher registration
with a listener now functions properly with SSL.

The bug has been fixed in which Database Configuration Assistant (DBCA) 
caused database registration in the directory to fail for Oracle 
Internet Directory on Windows. (1266289)

The bug has been fixed in which each user required an individual 
sqlnet.ora file. Multiple users can now share one sqlnet.ora file on a 
client machine.

The bug has been fixed in which the listener redirect impairs enterprise 
user security and prevents users from connecting as sysdba. (1113580)

Oracle Enterprise Security Manager (ESM) will now display an initial 
login box when it starts up. You no longer have to logout and login 
again with the proper privileges. However, when using Microsoft Active 
Directory, at startup ESM will still perform an automatic login to the 
directory using native authentication. (1098580)

The bug has been fixed in which ESM failed to read the sqlnet.ora file, 
which prevented configuration of ESM to use Net8 features such as naming 
and ASO encryption. (1368685)

The bug has been fixed in which removing domain administrators using ESM 
deleted any existing database ACLs in that domain. (1298185) 
