| Summary | The Baltimore security kit has been removed in Orbix 6.3.6, this has been deprecated for some time and OpenSSL has been available as an alternative. This is now the only option for C on Orbix and modernizes the solution. |
|---|---|
| Article Number | 36985 |
| Environment | Orbix 6.3.6 All Supported Platforms |
| Question/Problem Description |
Where is the Baltimore Security Kit in Orbix 6.3.6?
What security kit should I use in Orbix 6.3.6? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution |
In previous Orbix releases, the runtime could be configured to use either the Baltimore security toolkit or OpenSSL for C , and the Baltimore security toolkit or Java JSSE/JCA for Java.
In Orbix 6.3.6, the OpenSSL toolkit is the default and only TLS toolkit for C , and the Java JSSE/JCA toolkit is the default and only TLS toolkit for Java. Support for the Baltimore toolkit has been removed.
To migrate an older domain to use the newer JSSE/JCA toolkit, please ensure the following two configuration variables are set:
plugins:atli2_tls:use_jsse_tk = "true";
plugins:openssl_toolkit:shlib_name = "it_tls_openssl"; |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 19 December 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 19 December 2012 |
| First Published date: | 19 December 2012 |
#Orbix6
#Orbix
#KnowledgeDocs