2013-01-20 23:39:34 +01:00
|
|
|
Package: sshuttle
|
2015-04-18 14:27:35 +02:00
|
|
|
Version: 0+git
|
2015-04-18 14:14:33 +02:00
|
|
|
Architecture: all
|
2013-01-20 23:39:34 +01:00
|
|
|
Maintainer: Jim Wyllie <jwyllie83@gmail.com>
|
2015-04-18 14:29:26 +02:00
|
|
|
Depends: autossh, iptables, python (>= 2.6)
|
2015-04-18 14:29:54 +02:00
|
|
|
Section: net
|
2013-01-20 23:39:34 +01:00
|
|
|
Priority: optional
|
2015-04-18 14:25:05 +02:00
|
|
|
Homepage: http://github.com/sshuttle/sshuttle
|
2015-04-18 14:25:57 +02:00
|
|
|
Description: "Full-featured" VPN over an SSH tunnel
|
|
|
|
|
It allows full remote access somewhere where all you have is an SSH
|
|
|
|
|
connection. It works well if you generally find yourself in the
|
|
|
|
|
following situation:
|
2013-01-20 23:39:34 +01:00
|
|
|
.
|
|
|
|
|
- Your client machine (or router) is Linux, FreeBSD, or MacOS.
|
|
|
|
|
- You have access to a remote network via ssh.
|
|
|
|
|
- You don't necessarily have admin access on the remote network.
|
|
|
|
|
- You do not wish to, or can't, use other VPN software
|
|
|
|
|
- You don't want to create an ssh port forward for every
|
|
|
|
|
single host/port on the remote network.
|
|
|
|
|
- You hate openssh's port forwarding because it's randomly
|
|
|
|
|
slow and/or stupid.
|
|
|
|
|
- You can't use openssh's PermitTunnel feature because
|
|
|
|
|
it's disabled by default on openssh servers; plus it does
|
|
|
|
|
TCP-over-TCP, which has suboptimal performance
|
|
|
|
|
.
|
|
|
|
|
It also has hooks for more complicated setups (VPN-in-a-SSH-VPN, etc) to allow
|
|
|
|
|
you to set it up as you like.
|
