Search results

With bubblewrap you don't generally jail a user, but an environment. As a web server, it's up to the application to define users and then you can use a virtual host to only do certain things for all who enter (bubblewrap can be a tool for that). Run with limited access to specific directories...

Sorry, the error didn't make it into the response. You really would be better served through a ticket. Follow this path: https://store.litespeedtech.com/store/submitticket.php?step=2&deptid=2

There's just been an update in OpenLiteSpeed related to ModSecurity using the latest LibModSecurity binaries. You can get the updates by doing: `/usr/local/lsws/admin/misc/lsup.sh -b -e 1.7.13 `. If the problem continues, you should open a ticket. Thanks!

No, it should be fine.

To remove lsmcd: - sudo /usr/local/lsmcd/bin/lsmcdctrl stop - sudo systemctrl disable lsmcd - sudo rm -rf /dev/shm/lsmcd - sudo rm -rf /tmp/lsmcd - sudo rm -rf /usr/local/lsmcd ...and you should be clean to install memcached.

Are you using lsmcd (memcached) because of Litespeed WordPress Caching?

Clearly you need either lsmcd or memcached for your product. Through telnet you always get v1.0.0 because that's the API version. To get the actual version run: sudo /usr/local/lsmcd/bin/lsmcd -v lsmcd is better than memcached if you're using the separate user feature of it, which I suspect...

The next step would be to strace the lsphp process to see if it's waiting for lsmcd. We'll need you to try to identify the lsphp process to run this strace if it goes to that point. Let us know if you're still having that problem and we'll help you with that. Thanks, Bob Perper...

Hey, let's rule out lsmcd for sure. If you stop the lsmcd service and restart it that ought to free it up. What I might suggest is clearing everything along the way: ``` sudo /usr/local/lsmcd/bin/lsmcdctrl stop sudo rf -rf /dev/shm/lsmcd sudo /usr/local/lsmcd/bin/lsmcdctrl start ``` Then try...

Sorry, yes context is important here. I responded because you mentioned your lsmcd log and I'm the lsmcd specialist. Let me get your back to an OLS specialist who might understand the initial issue better. You'll get a message shortly. Thanks. Bob Perper

If this is an LSMCD product error I might suggest the following: - We have a new release of LSMCD. You should check it out, compile and install it. - Before bringing up LSMCD delete your existing shared memory files: `sudo rm -rf /dev/shm/lsmcd` If the problem continues, please include your...

Jegan, A couple of things I learned in testing with David today: - I was using curl to do my testing. In the request, the file being requested (not the one being executed) must be a dynamic file - in the case we tested here a php file. I saw in your testing that you were testing with...

Jegan, Don't do anything quite yet, as I didn't properly describe the issue to David. I'll reproduce it here and give it to him. Thanks, Bob Perper

There have been a number of updates to my mod_security posting already. Looks like they're taking it on...

Posting is here: https://github.com/SpiderLabs/ModSecurity/issues/2332 If you learn anything, please post it here, if I learn anything, I'll also post it here. Thanks! Bob Perper rperper@litespeedtech.com

I had an inspectFile test I used with Enterprise LiteSpeed Web Server so I modified it to run with OpenLiteSpeed, turned on debug logging as you did and ran into the same issue: ``` [1591380817] [/?b=inspectfail] [4] Executing chained rule. [1591380817] [/?b=inspectfail] [4] (Rule: 0) Executing...

Jegan, Good job getting the auditlog. That shows that ModSecurity claimed to run your script. Let me try to reproduce it here and I'll get back to you. Bob

Hi, my name is Bob Perper and I'm a developer and support technician here at Litespeed Technologies. When it comes to mod_security, OpenLiteSpeed simply passes the rule to the engine, it's up to the mod_security engine to run your program. So since there are not any known problems with running...

Paulo, Just to let you know that v1.5.8 has been released and it includes support for the redirection using LS_STDERR_LOG that we discussed. Give it a try - if you have any problems, please let us know. Thanks.

Paulo, Sorry, my prior message was incorrect; there currently is no way to do it with OpenLitespeed. However, it can be done with Enterprise Litespeed by setting the environment variable LS_STDERR_LOG=<fully qualified file name> in the Environment configuration of the node app server...