Co-authored-by: KaKi87 <KaKi87@pm.me> Reviewed-on: #13 Co-authored-by: Androz2091 <firstname.lastname@example.org> Co-committed-by: Androz2091 <email@example.com>
|2 months ago|
|data||2 years ago|
|lib||4 months ago|
|src||2 months ago|
|.gitignore||5 months ago|
|LICENSE.md||3 years ago|
|README.md||4 months ago|
|config.example.js||5 months ago|
|main.js||2 months ago|
|package.json||4 months ago|
|screenshot.png||5 months ago|
|screenshot2.png||4 months ago|
|strings.js||2 months ago|
|yarn.lock||4 months ago|
This project is, at the same time, an SSH server, an SSH client, and a password manager.
yarn keygento generate an SSH key pair
config.jsand specify a custom port
yarn installto install dependencies
yarn startto start the SSH server
Stop : press
Ctrl + C
The account manager at
@sshception/account is unit-tested.
- Connect using any SSH client
- Follow the steps
Automated TUI/CLI selection is based on terminal width.
Manual selection can be done using an
IS_CLI environment variable, e.g.
ssh -o "SetEnv IS_CLI=" ssh.kaki87.net.
Why should I use SSHception ?
It is open source.
This project is released under the MIT license.
It is multiplatform.
Firstly, the server can run on any platform supporting NodeJS.
Secondly, the server can be accessed from any SSH client.
It respects your privacy.
Your data is encrypted using the AES-256 asymmetric encryption algorithm using your own as password.
The standard TOTP 2FA is supported.
Why shouldn't I use SSHception ?
No direct connection.
Since this project is a server-side service, the SSH connection to your target host is not initiated from your client itself but from the SSHception server-side client then streamed to you.
Therefore, your SSH client-side logs will always log your connections to the SSHception server and your SSH server-side logs will always log the connections from the SSHception server.