OpenSSL multithreading callbacks are not handled in bvC-Oracle. This is causing bvC-Oracle queries to hang or give unknown errors when scope to more than one target.

Article:TECH169625  |  Created: 2011-09-15  |  Updated: 2011-09-15  |  Article URL http://www.symantec.com/docs/TECH169625
Article Type
Technical Solution


Issue



  1. OpenSSL multithreading callbacks are not handled in bvC-Oracle. This is causing bvC-Oracle queries to hang or give unknown errors when scope to more than one target
  2.  bvC-Oracle DLL’s gets loaded into specific memory addresses. If FIPS mode is enabled and these binaries not get loaded at specified memory addresses(this may be because of a particular address space is occupied by another DLL) then FIPS self-test will fail.  The error message box entitled: "OpenSSL:FATAL"; and it states: ".\fips\fips.c(146): OpenSSL internal error, assertion failed: FATAL FIPS SELFTEST FAILURE" will be shown. Restarting the application may allows DLL’s to load  to their  proper location, allowing the self-test to pass.
  3. This self test for bvC-Oracle DLL’s can be disabled by setting registry DWORD key “DisableFipsTest” to 1.

Environment



CCS 10.5.1 and CCS 10.5.1 PCU 2011- 3

 


Solution



Apply Quick Fix 20112 to resolve this issue. After applying the quick fix add and enable the DWORD key “DisableFipsTest” at the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\BindView\bv-Control\UNIXShared
               
Note: After the DisableFipsTest key is enabled BV-Control for Oracle 10.5.1 will work in non-FIPS compliant mode.

( Note : QF 20112 will be included in PCU 2011-4, at the time of writing the article PCU 2011-4 is not yet released )




Article URL http://www.symantec.com/docs/TECH169625


Terms of use for this information are found in Legal Notices