>
> The libxmlsec source code tarball will be in the SFW gate and use
> a build harness similar to other libxml2 libraries. It will be
> configured and compiled with only its libxmlsec-openssl module
> to support OpenSSL as the underlying encryption library.
> The libxmlsec-openssl crypto module is libxmlsec's default
> module, is MIT licensed and can make use of Sun's OpenSSL crypto
> engine to use the Userland Encryption Framework. Legal approval for
> this usage is covered by OSR 7806.
> A follow up ARC cases may be filed after RFE#6479874 integrates
> in our OpenSSL implementation to improve crypto engine usage.
> A future ARC case could also switch us from using the OpenSSL
> module to a new module with more direct access to the crypto framework.
> Such a module would first need to be integrated in the community
> project.
so, any dependency on a particular version of OpenSSL's lib{crypto,ssl} ?
doesn't this case require an ARC contract against PSARC/2003/500 for the
import of OpenSSL ?
Kais
