mitten
is a drop-in replacement for SSH that brings internet connection
to the machines without it, and enables easy file transfer between the local
and remote machines.
There is built-in authentication, so only the user inside of the mitten session
can use the connection and have the access to the local files.
A common use case for mitten is installing packages in Conda/Miniforge environments which rely on fetching the them from the internet.
Normally, on machines with no internet access, calls like these fail or hang:
$ ssh supercomp
supercomp> curl -I https://unkaktus.art
curl: (7) Failed to connect to unkaktus.art port 443: Network is unreachable
With mitten
, they work through your local connection:
$ mitten supercomp
βββββ
ββ ββ
βββ ββ
βββββ βββββββββ
β β βββ
β β mitten β
β β magic! ββ
βββββ βββ
βββββββββββββ
supercomp> curl -I https://unkaktus.art
HTTP/1.1 308 Permanent Redirect
Mitten magic!
To easily transfer files between the local machine and the remote,
use mittenfs
command after logging in, which provides sftp
interface:
$ mitten supercomp
supercomp> mittenfs
supercomp> sftp> get local_file.dat .
supercomp> sftp> lls
local_file.dat
Mitten magic!
- Download and install the binary for your platform. For example, for Linux on AMD64:
curl -L -o mitten https://github.com/unkaktus/mitten/releases/latest/download/mitten-linux-amd64
mkdir -p ~/bin
mv mitten ~/bin/
chmod +x ~/bin/mitten
Add $HOME/bin into your $PATH into your .bashrc:
export PATH="$HOME/bin:$PATH"
-
Install Go (https://go.dev,
brew install go
,conda install go
) -
Build
mitten
:
go install github.com/unkaktus/mitten@latest
- Add
$HOME/go/bin
to your$PATH
:
export PATH="$HOME/go/bin:$PATH"
You would probably want to have it permanently, so put it into your shellrc.
Certain apps, such as opkg
of OpenWRT, don't support HTTP proxy authentication.
One can disable this authentication by setting MITTEN_DISABLE_PROXY_AUTH=yes
.
Note that it is, of course, insecure.
Behind the scenes, mitten launches an HTTP(S) proxy, and starts an SSH session with
forwarding of the local proxy port to the remote machine. After the connection is made,
and the user logged in, the shell prompt is getting detected. Then, mitten types in
a shell command which exports http_proxy
environment variables with the address and
authentication credentials set pointing to the forwarded connection. Because of this,
only the current SSH session has the password available, so other users and other
sessions are not able to use the proxy. After all these steps are done, the mitten
thumbs-up banner is displayed, and the user can use any tools that automatically pick up
the HTTP proxy configuration to access internet resources.