-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to block dangerous bash commands like RM as root? #826
Comments
Use the permission system to prevent users from creating/editing events, unless you want to give them that power. You can also remove the Shell Plugin from the system if it is too powerful for your needs. |
Hi, thanks for the reply. you cannot do something like a text validator? like if detected rm or /usr/bin/rm it will give a notice/error? |
oh wait.. io found this in the plugin.. i can set the UID/GID. which means people cannot mess around areas that are root only. I think this will work.. will test it later |
ok i set the UID/GID to the local non root user. (1002/1002) and provided the home directory of that said user. but the task is failing when i set a cron to delete something in the /tmp folder Job ID: jm3gg2d321f Job failed at 2024/11/13 22:20:00 (GMT+0). |
Change the Shell Plugin executable location to absolute, instead of a relative position: Change this:
To this:
|
Summary
how to prevent dangerous commands as root ?
Steps to reproduce the problem
Your Setup
hosted on AWS. uses nginx as reverse proxy with single chronicle master instance
Operating system and version?
Linux 2023
Node.js version?
18.18.0
Cronicle software version?
0.9.61
Are you using a multi-server setup, or just a single server?
Single
Are you using the filesystem as back-end storage, or S3/Couchbase?
local filesystem
Can you reproduce the crash consistently?
yes
Log Excerpts
The text was updated successfully, but these errors were encountered: