Spawn shells anywhere. Fully peer-to-peer, authenticated, and end to end encrypted.
npm i -g hypershell
# Create keys
hypershell-keygen [-f keyfile] [-c comment]
# Create a P2P shell server
hypershell-server [-f keyfile] [--firewall filename]
# Connect to a P2P shell
hypershell [-f keyfile] <server name or public key>
# Local tunnel that forwards to remote host
hypershell [-L [address:]port:host:hostport] <server name or public key>
# Copy files (download and upload)
hypershell-copy [-f keyfile] <[@host:]source> <[@host:]target>
Use --help
with any command for more information.
Keys are automatically created with a default filename on first run.
Otherwise, you can first do:
hypershell-keygen
Just connect to servers (they have to allow your public key):
hypershell <server name or public key>
You could also create a server:
hypershell-server
~/.hypershell/authorized_peers
file will be empty, denying all connections by default.
Public keys can be added to the list to allow them in real-time.
There will be a file ~/.hypershell/known_peers
.
Add named peers to the file like for example:
# <name> <public key>
home cdb7b7774c3d90547ce2038b51367dc4c96c42abf7c2e794bb5eb036ec7793cd
Now just hypershell home
(it saves you writing the entire public key).
Similar to scp
. It works with files, and with folders recursively.
For the next examples, remote_peer
is a name that can be added to the known_peers
file.
Upload a file from your desktop to a remote server:
hypershell-copy ~/Desktop/file.txt @remote_peer:/root/file.txt
Download a file from a remote server to your desktop:
hypershell-copy @remote_peer:/root/database.json ~/Desktop/db-backup.json
Note: in the future, the @
might be removed.
You can also use the public key of the server directly (without @
):
hypershell-copy ~/Desktop/some-folder cdb7b7774c3d90547ce2038b51367dc4c96c42abf7c2e794bb5eb036ec7793cd:/root/backup-folder
It creates a local server, and every connection is forwarded to the remote host.
In this example, creates a local tunnel at 127.0.0.1:2020
(where you can connect to),
that later gets forwarded to a remote server which it connects to 127.0.0.1:3000
:
hypershell remote_peer -L 127.0.0.1:2020:127.0.0.1:3000
Instead of remote_peer
you can use the server public key as well.
To have multiple servers, you need multiple keys.
Generate another key:
hypershell-keygen -f ~/.hypershell/my-server
Now create a new shell server:
hypershell-server -f ~/.hypershell/my-server --firewall ~/.hypershell/my-server-firewall
The client also accepts -f
in case you need it.
MIT