summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOssama Othman <ossama-othman@users.noreply.github.com>2004-07-31 00:50:14 +0000
committerOssama Othman <ossama-othman@users.noreply.github.com>2004-07-31 00:50:14 +0000
commit0a148fee9956bf45fa795d7a5a3dc80534f9f866 (patch)
treeb5b93a5141429250dce0f477438083ca9f05c3b0
parenta32a1d2b2c2fd4457228b0eaa0bc66b06fe53a70 (diff)
downloadATCD-0a148fee9956bf45fa795d7a5a3dc80534f9f866.tar.gz
ChangeLogTag:Fri Jul 30 17:48:53 2004 Ossama Othman <ossama@dre.vanderbilt.edu>
-rw-r--r--TAO/docs/releasenotes/index.html64
1 files changed, 32 insertions, 32 deletions
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html
index 044c46e8baa..20946967024 100644
--- a/TAO/docs/releasenotes/index.html
+++ b/TAO/docs/releasenotes/index.html
@@ -624,7 +624,7 @@ are guarded by the same #ifdef preprocessor directives as before.
The mechanism for processing multiple IDL files in a single execution has
changed. Instead of spawning a separate process for each IDL file, the
IDL compiler now processes the files sequentially in a single process.
-Note that, for each file, execution of the preprocessor spawns a new
+Note that, for each file, execution of the preprocessor spawns a new
process, as it always has.
</li>
</ul>
@@ -1636,7 +1636,7 @@ functionality of the <a href="http://www.omg.org/cgi-bin/apps/doc?formal/02-03-1
<p>
In particular, it implements the most of the CORBA <a href="../../orbsvcs/orbsvcs/SecurityLevel1.idl">SecurityLevel1 API</a>,
in addition to some of <a
- href="../../orbsvcs/orbsvcs/SecurityLevel2.idl">SecurityLevel2</a>.
+ href="../../orbsvcs/orbsvcs/SecurityLevel2.idl">SecurityLevel2</a>.
Of the transport protocols described in the above specification, only
SSLIOP is supported. Documentation for TAO's SSLIOP pluggable
transport is available <a href="../Security/index.html">here</a>.
@@ -1667,7 +1667,7 @@ defined policies:
<blockquote><code>
SecurityLevel2::QOPPolicy<br>
SecurityLevel2::EstablishTrustPolicy<br>
- SecurityLevel3::ContextEstablishmentPolicy<br>
+ SecurityLevel3::ContextEstablishmentPolicy<br>
</blockquote></code>
</li>
</ol>
@@ -1721,28 +1721,28 @@ Implemented <tt>SecurityLevel2::PrincipalAuthenticator</tt> support for
SSLIOP. In particular, a SSLIOP-specific <tt>SecurityReplaceable::Vault</tt>
implementation is now available.</li>
<li>
- Implemented basic (stateless) CSIv2 support. Advanced CSIv2
- features, such as identity assertion, are currently under
- development.
+ Implemented basic (stateless) CSIv2 support. Advanced CSIv2
+ features, such as identity assertion, are currently under
+ development.
</ul>
</ul>
<h4>Current Status</h4>
<ul>
<li>
- Began implementation of the interfaces in the
- <tt>SecurityReplaceable</tt> IDL module. They provide the
- ability to replace key security components in the ORB with
- another implementation with ease. Thus, the security
- components in the ORB become highly extensible.</li>
+ Began implementation of the interfaces in the
+ <tt>SecurityReplaceable</tt> IDL module. They provide the
+ ability to replace key security components in the ORB with
+ another implementation with ease. Thus, the security
+ components in the ORB become highly extensible.</li>
<li>
- Development of core <tt>SecurityLevel2</tt> interfaces such as
- <tt>Credentials</tt>, <tt>SecurityManager</tt>,
- and <tt>PrincipalAuthenticator</tt> has been halted in favor
- of Adiron's <tt>SecurityLevel3</tt> interfaces</li>
+ Development of core <tt>SecurityLevel2</tt> interfaces such as
+ <tt>Credentials</tt>, <tt>SecurityManager</tt>,
+ and <tt>PrincipalAuthenticator</tt> has been halted in favor
+ of Adiron's <tt>SecurityLevel3</tt> interfaces</li>
<li>
- Advanced CSIv2 features, such as identity assertion, are
- currently under testing.</li>
+ Advanced CSIv2 features, such as identity assertion, are
+ currently under testing.</li>
</ul>
<h4>Schedule</h4>
<ul>
@@ -1751,21 +1751,21 @@ implementation is now available.</li>
<ul>
<li>
- Complete integration of the Common Secure Interoperability
- version 2 (CSIv2) protocol defined in the <a
- href="http://www.omg.org/cgi-bin/doc?formal/04-03-12">CORBA
- 3.0.x</a> core specification, and the <a
- href="http://www.omg.org/technology/documents/formal/atlas.htm">Authorization Token Layer Acquisition Service (ATLAS)</a>.
- <p>
- CSIv2 and ATLAS address many of the shortcomings of the
- current CSIv1-based Security Service. Overviews of each are
- available on the <a href="http://www.omg.org/technology/documents/formal/omg_security.htm">OMG Security</a> web page.
- <blockquote><em>
- Note that CSIv2 as defined by the CORBA 3.0.x specification
- has no API so TAO's implementation will use a slightly
- <a
- href="http://adiron.com/ORBAsec/3.5.0/docs/SL3/#SecurityLevel3API">modified API</a> currently used by several ORBs defined by Adiron LLC.
- </em></blockquote>
+ Complete integration of the Common Secure Interoperability
+ version 2 (CSIv2) protocol defined in the <a
+ href="http://www.omg.org/cgi-bin/doc?formal/04-03-12">CORBA
+ 3.0.x</a> core specification, and the <a
+ href="http://www.omg.org/technology/documents/formal/atlas.htm">Authorization Token Layer Acquisition Service (ATLAS)</a>.
+ <p>
+ CSIv2 and ATLAS address many of the shortcomings of the
+ current CSIv1-based Security Service. Overviews of each are
+ available on the <a href="http://www.omg.org/technology/documents/formal/omg_security.htm">OMG Security</a> web page.
+ <blockquote><em>
+ Note that CSIv2 as defined by the CORBA 3.0.x specification
+ has no API so TAO's implementation will use a slightly
+ <a
+ href="http://adiron.com/ORBAsec/3.5.0/docs/SL3/#SecurityLevel3API">modified API</a> currently used by several ORBs defined by Adiron LLC.
+ </em></blockquote>
</li>
</ul>