Guarantee secure, efficient and native remote access to the project’s various Linux teams (servers and clients).
Options compared
| Remote access system | integration | Protocol | security | requirements | Recommended use |
|---|---|---|---|---|---|
| SSH (OpenSSH) | Native | SSH | High | Cap extra | Control per terminal |
| Cockpit | Optional | HTTPS | High | Port 9090 and browser | Graphic management |
| VNC (TigerVNC, etc.) | Optional | VNC | average | Active GUI | remote desktop |
| Webmin | Optional | HTTPS | average | Web browser | Visual administration |
Decision criterion used
- Native integration: We prioritize tools that already come with the system or that are easy to install.
- Security: We look for secure and encrypted protocols (such as SSH or HTTPS).
- Efficiency: Lightweight tools that do not load the system unnecessarily.
- Ease of use: Familiar commands and easy-to-access environments.
- System role: A server is not the same as a basic client. Each will have a suitable tool.