Technical FAQs - FreeSSL
Q: What is FreeSSL?
A: FreeSSL is an Orbacus OCI plugin that allows for IIOP communication over a secure SSL connection. It provides authentication, privacy, and integrity and ensures that Orbacus clients and servers can communicate securely over any network.
Q: Can Orbacus applications use both secure and insecure connections?
A: Yes, applications can use any combination of secure and insecure connections. This is under complete control of the developer and can be enabled via a configuration file.
Q: Does FreeSSL comply with the OMG security service specification?
A: No, FreeSSL does not implement the security service specification from the OMG. FreeSSL is a propriety security implementation that is not based on any existing specification.
Q: What toolkits are compatible with FreeSSL?
A: For C++, FreeSSL requires OpenSSL (http://www.openssl.org) version 0.9.7. Version 0.9.7g of the toolkit is recommended. Note that older and newer versions of OpenSSL have not been tested with FreeSSL and are not guaranteed to work.
For Java, FreeSSL can use either the iSaSiLk/JCE toolkits from IAIK (http://jce.iaik.tugraz.at/products/index.php) or the Sun JSSE toolkit, which comes bundled with J2SE 1.4 and up.
Please see the Orbacus documentation for more details on these toolkits.
Q: Are Orbacus Services compatible with FreeSSL?
A: No, currently Orbacus services are not compatible with FreeSSL. These services would be required to be FreeSSL aware and, as FreeSSL is not part of the standard Orbacus distribution, it is not possible to enable FreeSSL in these services.
Q: What certificates formats are supported by FreeSSL?
A: FreeSSL supports DER encoded certificates/keys and PKCS12 encoded certificate/key files.
