Bug#1113779: RFP: shwim -- Peer-to-peer terminal sharing
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
* Package name : shwim
Version : 25.9.0
Upstream Contact: meejah
* URL : https://github.com/meejah/shwim
* License : MIT/Expat?
Programming Lang: Python
Description : Peer-to-peer terminal sharing
SHell WIth Me lets a “host” share their terminal with a “guest” peer
on another computer.
This combines the cryptography of Magic Wormhole (via Fowl) and the
terminal-sharing of tty-share into a secure, end-to-end encrypted,
peer-to-peer terminal sharing application.
The Host computer runs shwim by itself, producing a <magic-code>. The
Guest computer runs shwim <magic-code>.
You are now sharing a single terminal running on “host”. Beware: the
guest can type, run commands, etc. so only do this with humans you
would hand your local keyboard over to.
The Host may pass --read-only to ignore input from the Guest.
The ShWiM terminal UI running, showing a connection to the mailbox
server, generated code but no peer yet Slightly Longer Explanation
Once the two things happen (i.e. “shwim” on the host and “shwim ” on
the guest), there is a secure tunnel between both computers. The host
will decide a random port and run tty-share as a server; the guest
will run tty-share as a client.
On both computers, tty-share will be running as a subprocess with
correct options to do networking via Magic Wormhole only. All raw-mode
terminal I/O is forwarded to this tty-share process so things like
curses etc work as expected.
Once either side exits, the networking forwarding is done – there is
no long-term credential sharing or any other network set preserved or
altered on the “host” nor “guest” computers.
----
tty-share and wormhole are already in debian, this should be pretty
easy to package.
Reply to: