- Minor
The WebUI element to add ssh keys to the management user has a bug that it is too restrictive and does not support advanced ssh keys. Please modify the regex or validation function to account for the additional valid options present in an authorized_key file.
from="192.168.1.0/24,host.example.com"Restrict login to keys coming from specific IPs or hostnames. You can specify multiple sources and CIDR ranges.
command="/home/user/system/exec_check.sh"Force a command to be run on login, ignoring anything provided by the client.
no-port-forwarding Disables TCP forwarding capabilities (e.g., -L, -R, -D options in SSH).
no-X11-forwarding Disables X11 forwarding.
no-agent-forwarding Disables SSH agent forwarding.
no-pty Prevents the allocation of a pseudo-terminal. Useful to lock down command-executing keys.
permitopen="127.0.0.1:3306" Restricts port forwarding to only specific hosts/ports.
environment="FORCE_COLOR=true" Set environment variables for the session.
tunnel="1" Request a tun device when logging in. Used for VPN-like behavior.
Current workaround is to manually edit the root.pubkey file in terminal.