VirtualBox (sometimes) not starting/hanging after recent openssl updates
Warren Block
wblock at wonkity.com
Mon Mar 30 21:49:39 UTC 2015
On Mon, 30 Mar 2015, Mario Lobo wrote:
> On Mon, 30 Mar 2015 22:21:51 +0200
> Christoph Moench-Tegeder <cmt at burggraben.net> wrote:
>
>> Hi,
>>
>> ## Ivo Karabojkov (karabojkov at kit.bg):
>>
>>> I've explained my tests already to the thread you mention. Here is
>>> my ldd output from a working system:
>>> # ldd /usr/local/lib/virtualbox/VBoxRT.so
>>> /usr/local/lib/virtualbox/VBoxRT.so:
>>
>>> libcrypto.so.7 => /lib/libcrypto.so.7 (0x8026a8000)
>>
>> Unless I completely mis-grepped your mail, this is the only libcrypto
>> pulled in by your VBoxRT.so, so it's not surprising that your system
>> is fine :)
>> The trouble starts when /usr/local/lib/libcrypto.so.8 and the
>> libcrypto.so.7 as above are referenced by the same VBoxRT.so.
>> Mind, the libcrypto.so.8 is part of "openssl from ports", so unless
>> you have that installed, you should be safe from _this_ problem.
>>
>> Regards,
>> Christoph
>>
>
> Nope!
>
> I have:
>
> /usr/local/lib/virtualbox/VBoxRT.so:
> (snip)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x8026a7000)
> libcrypto.so.7 => /lib/libcrypto.so.7 (0x80431d000)
> libcrypt.so.5 => /lib/libcrypt.so.5 (0x804fee000)
>
>
> and mine is fine too!
Mine links only to 8, but does not work:
/usr/local/lib/virtualbox/VBoxRT.so:
...
libssl.so.8 => /usr/local/lib/libssl.so.8 (0x80244d000)
More information about the freebsd-emulation
mailing list