Overview
quickssh lets you reach the systems behind your VPNs from a single app: servers, remote desktops, files and databases. Every VPN runs in its own isolated container; your computer's network is left alone.
When it helps
- You need to stay connected to several customers' or environments' VPNs at the same time.
- VPN clients break your computer's DNS and routing.
- You want connection details (address, user, password, route) in one tidy place.
- Your team reaches the same servers, but you don't want to hand the passwords to everyone.
The parts
quickssh consists of two applications:
| Part | File | What it does |
|---|---|---|
| Server | quicksshd | Stores records, runs the VPN containers, connects to targets, enforces permissions, keeps the log. Runs on Linux. |
| Client | quickssh | The interface and the command line. Shows results and passes your input to the server. |
The server is used in one of two ways:
- Local: the server is on your own computer. The client starts it by itself; there is nothing else to install.
- Central: the server is on a shared Linux machine of the team. Clients connect to it over SSH; records and passwords stay there.
To the client the two are the same: same screens, same commands.
Key concepts
- VPN profile: the definition of a VPN connection. When started it runs in its own container and offers a jump host and a SOCKS5 proxy.
- Session: a target to connect to. Its type can be SSH, SFTP, FTP, RDP, VNC or a database.
- Route: how the session reaches its target: directly, through a VPN or through another SSH session. Hops can be chained (VPN → VPN → SSH → SSH).
- Group and tag: for organizing and searching records.
Next step
Start with Installation, then add your first VPN and session with Getting started.