RFR: 8152084: Introduction of ssliop protocol to corbaloc
Andrew Dinn
adinn at redhat.com
Wed May 4 14:53:22 UTC 2016
On 04/05/16 15:36, Tomasz Adamski wrote:
> I'm proposing this extension from practical reasons as it would
> enable configuration of fully secured iiop invocations - the feature
> that was present in ORB implementation that we used previously
> (JacORB). ORB specification allows adding new corbaloc protocols if
> necessary:
>
> "This specification only defines use of iiop with corbaloc. New
> protocols can be added to corbaloc as required. Each new protocol
> must implement the <future_prot_addr> component of the URL and define
> described in corbaloc URL." ORB Architecture Specification v3.3, Part
> 2: CORBA Interoperability, 7.6.10.6
Just to dispel any idea that this has been plucked out of thin air by
the JacORB implementors I'll note that there appears to be both a
standard for and more than one implementation of ssliop.
Regarding implementations, OpenORB and TAO also implemented it.
As regards standardization I think the relevant info is in the interop
documentation found at http://www.omg.org/spec/CORBA/3.3/. Look in part
2 of the spec dealing with interoperability and search for IIOP/SSL.
Tomek may be able to clarify whether that provides all the relevant
information.
regards,
Andrew Dinn
-----------
More information about the core-libs-dev
mailing list