mirror of
https://github.com/Dokploy/dokploy.git
synced 2026-09-14 11:06:15 +05:00
bbde5ebbc3
Reaching a server implied being able to open an SSH root shell on it: the /terminal websocket only checked that the server was in the caller's accessible set, so granting a server to a developer necessarily granted root on it. Add a server.terminal action, assignable on custom roles, and require it on the remote-server terminal websocket on top of server access. Owner/admin keep it through the enterprise bypass; the local host terminal stays owner/admin only. A migration grants server.terminal to existing custom roles that already have server.read, which is the permission that surfaces the terminal today, so current setups keep working. Roles without a server entry are left alone. Note: server.create still implies root execution (server.update persists server.command and server.setup runs it over SSH), reflected in the Create description in the role editor. |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| auth-schema2.ts | ||
| auth-schema.ts | ||
| esbuild.config.ts | ||
| package.json | ||
| tsconfig.json | ||
| tsconfig.server.json | ||
| tsconfig.server.no-decl.json | ||