Milestones
List view
tidegate's parts are planned, but none of them work together yet. The first goal is one path through the whole system: an administrator reaches an SSH host through tidegate, and tidegate records the session. Every part on that path exists in its simplest form that works. Everything else comes later. Done when: - An administrator signs in to tidegate with a local password and a TOTP code. - They add an SSH host and give themselves a role that lets them reach it and doesn't expire. - They open an SSH session to the host with the tidegate CLI. The session goes through the web-gateway, which accepts users' connections, and an ssh-proxy, which connects to the host. tidegate records the session.
Due by December 31, 2026•12/28 issues closed