Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.rst #56

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.rst #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
sshuttle: where transparent proxy meets VPN meets ssh
sshuttle: where transparent proxy meets VPN meets SSH
=====================================================

As far as I know, sshuttle is the only program that solves the following
common case:

- Your client machine (or router) is Linux, FreeBSD, or MacOS.

- You have access to a remote network via ssh.
- You have access to a remote network via SSH.

- You don't necessarily have admin access on the remote network.

Expand All @@ -15,13 +15,13 @@ common case:
admin and you just got frustrated with the awful state of
VPN tools.

- You don't want to create an ssh port forward for every
- 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
- You hate OpenSSH's port forwarding because it's randomly
slow and/or stupid.

- You can't use openssh's PermitTunnel feature because
- 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 terrible performance (see below).

Expand Down