chiralsoftware

I'm getting this issue on Amazon Linux 2023. I'm doing install with source. Install with package didn't work, as it had some conflict with cryptography module which I couldn't figure...

Same issue for me, Jetty 11.0.20, when using setuid. jetty.sh starts, creates the state file as root (not writable by non-root), launches the process as non-root, and that process then...

As a not very beautiful hack to let me upgrade my jetty installations, I added this at line 155 in `jetty.sh`: ` chmod ugo+w $STATEFILE`

This situation still exists in Jetty 12.0.9. For Setuid module to work, I need to add that line at 155 in jetty.sh. I realize the right answer might be, don't...