summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTzafrir Cohen <tzafrir.cohen@xorcom.com>2012-01-19 19:33:20 +0000
committerTzafrir Cohen <tzafrir.cohen@xorcom.com>2012-01-19 19:33:20 +0000
commit765ac4f59578496e0c20283fd65637154a9df50a (patch)
tree9b440b145b0db3283dedd5a74d8370ce1d22ff23
parentac5d52c3d028b186006df4acaab5a7d2dde74c02 (diff)
rapid-tunneling: update README about keys
git-svn-id: svn+ssh://xorcom/home/svn/debs/components/rapid-tunneling@10358 283159da-0705-0410-b60c-f2062b4bb6ad
-rw-r--r--README6
1 files changed, 2 insertions, 4 deletions
diff --git a/README b/README
index 40cca1e..62c0a61 100644
--- a/README
+++ b/README
@@ -41,10 +41,7 @@ Client
* Install the packages rapid-tunneling (base package) and
rapid-tunneling-gui (simple web interface).
* Package installs a user called rapid-tunneling for all the dirty work.
-* Due to original requirements, that is actually a "user" with uid 0.
- However the system should work just as well with this being a normal
- user.
-* The cleint only trusts servers for which it has the keys. Make sure it
+* The client only trusts servers for which it has the keys. Make sure it
knows the keys with which you sign on the server.
* The -gui places a web interface on http://<hostname>/support .
While technically this interface should only allow usage through
@@ -205,6 +202,7 @@ no-X11-forwarding,no-agent-forwarding,no-pty,permitopen="127.0.0.1:65534",comman
A key can also be used to flood the server's disk, which means that the
support user's quota should be limited.
+
The Client
~~~~~~~~~~
The client then sends the connection information over the already