Opened 6 years ago
#18134 new defect
Qt5 interface does not start with hardening, with qt-xcb enabled.
Reported by: | alarcher | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.2.22 |
Keywords: | hardening | Cc: | |
Guest type: | other | Host type: | Solaris |
Description
Hi, trying to package VirtualBox for OpenIndiana given that stack clash mitigation in illumos broken compatibility (VirtualBox panics).
https://github.com/OpenIndiana/oi-userland/pull/4569
Non-hardened builds run as expected while hardened builds fail to bring up the Qt5 interface.
alarcher@helios:/home/alarcher$ VirtualBox ld.so.1: VirtualBox: fatal: libQt5XcbQpa.so.5: open failed: No such file or directory ld.so.1: VirtualBox: fatal: relocation error: file /usr/lib/qt/5.8/plugins/amd64/platforms/libqxcb.so: symbol _ZN15QXcbIntegrationC1ERK11QStringListRiPPc: referenced symbol not found Killed
This runs properly as root and symbols were verified to be OK.
Trussing the execution does not help due to hardening.
The only reason I could come up with is that libqtxcb.so's RUNPATH uses $ORIGIN to pick the location of libQt5XcbQpa.so.5.
Is there a hard limitation in the hardening code regarding RUNPATH or is it a bug?
Thanks