weblogic-remote-console-2.4.17-linux.deb: File modes

[xalkina]

weblogic-remote-console-2.4.17-linux.deb installs the following directories with 0777 permissions:

weblogic-remote-console
weblogic-remote-console/backend
weblogic-remote-console/backend/libs
weblogic-remote-console/customjre
weblogic-remote-console/customjre/bin
weblogic-remote-console/customjre/bin/java
weblogic-remote-console/customjre/bin/keytool
weblogic-remote-console/customjre/conf
weblogic-remote-console/customjre/conf/sdp
weblogic-remote-console/customjre/conf/security
weblogic-remote-console/customjre/conf/security/policy
weblogic-remote-console/customjre/conf/security/policy/limited
weblogic-remote-console/customjre/conf/security/policy/unlimited
weblogic-remote-console/customjre/legal
weblogic-remote-console/customjre/legal/java.base
weblogic-remote-console/customjre/legal/java.datatransfer
weblogic-remote-console/customjre/legal/java.desktop
weblogic-remote-console/customjre/legal/java.logging
weblogic-remote-console/customjre/legal/java.management
weblogic-remote-console/customjre/legal/java.naming
weblogic-remote-console/customjre/legal/java.prefs
weblogic-remote-console/customjre/legal/java.security.sasl
weblogic-remote-console/customjre/legal/java.sql
weblogic-remote-console/customjre/legal/java.transaction.xa
weblogic-remote-console/customjre/legal/java.xml
weblogic-remote-console/customjre/legal/jdk.crypto.ec
weblogic-remote-console/customjre/legal/jdk.unsupported
weblogic-remote-console/customjre/lib
weblogic-remote-console/customjre/lib/security
weblogic-remote-console/customjre/lib/server
weblogic-remote-console/customjre/lib/jexec
weblogic-remote-console/customjre/lib/jspawnhelper
weblogic-remote-console/locales
weblogic-remote-console/resources
weblogic-remote-console/resources/nls

Additionally, and rightly so, it installs /opt/weblogic-remote-console/chrome-sandbox with mode 0755.

However, when the console is launched, it refuses to start with the following message:

[1205652:0720/094519.062268:FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/weblogic-remote-console/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

I'm not going to ask why on earth such an application requires suid to run...

[lfeigen]

We have tracked this down and the next release (in the fall) will have the fix. Thanks for noticing the issue.