This issue is fairly similar to issue 121, in that I'm unable to start Cerebro due to execution of the JDBC being prohibited. The difference is, instead of the filesystem's noexec option getting in the way, this time fapolicyd is interfering.
Aug 02 11:36:40 hostname cerebro[3210818]: /opt/cerebro/sqlite-3.34.0-47390f7e-7dd5-45d7-9a01-0635f335df40-libsqlitejdbc.so (Operation not permitted)
Aug 02 11:36:42 hostname cerebro[3210818]: /opt/cerebro/sqlite-3.34.0-cb416389-64b7-4ed6-9e52-5c710ec85a6c-libsqlitejdbc.so (Operation not permitted)
Normally, I would use the fapolicyd-cli command to add the driver file to the fapolicyd trust list, but each time the application starts, the JDBC driver file has a unique filename, so adding an existing file isn't a viable option. Note the hexidecimal characters above - those are different at each application startup.
Is there a known workaround for getting cerebro to play nice with fapolicyd? Can the JDBC connector be placed somewhere static, instead of created each time Cerebro starts?
This issue is fairly similar to issue 121, in that I'm unable to start Cerebro due to execution of the JDBC being prohibited. The difference is, instead of the filesystem's noexec option getting in the way, this time fapolicyd is interfering.
Normally, I would use the fapolicyd-cli command to add the driver file to the fapolicyd trust list, but each time the application starts, the JDBC driver file has a unique filename, so adding an existing file isn't a viable option. Note the hexidecimal characters above - those are different at each application startup.
Is there a known workaround for getting cerebro to play nice with fapolicyd? Can the JDBC connector be placed somewhere static, instead of created each time Cerebro starts?