summaryrefslogtreecommitdiff
path: root/app/lbxproxy/README
diff options
context:
space:
mode:
authorMatthieu Herrb <matthieu@cvs.openbsd.org>2008-09-14 13:18:31 +0000
committerMatthieu Herrb <matthieu@cvs.openbsd.org>2008-09-14 13:18:31 +0000
commit4cee52b4fab4efe9fce75872850b22f985c53049 (patch)
treee8195fa2e4166f017a95211ee3bc7e9be53c42a6 /app/lbxproxy/README
parent1c6f2f99d302b6e2e0bf6620e73dfe46aa5d338c (diff)
Remove deprecated applications (have been disabled for several month).
Diffstat (limited to 'app/lbxproxy/README')
-rw-r--r--app/lbxproxy/README15
1 files changed, 0 insertions, 15 deletions
diff --git a/app/lbxproxy/README b/app/lbxproxy/README
deleted file mode 100644
index 1854d3624..000000000
--- a/app/lbxproxy/README
+++ /dev/null
@@ -1,15 +0,0 @@
-Applications that would like to take advantage of the Low Bandwidth
-extension to X (LBX) must make their connections to an lbxproxy.
-These applications need to know nothing about LBX, they simply connect
-to the lbxproxy as if were a regular server. The lbxproxy accepts
-client connections, multiplexes them over a single connection to the X
-server, and performs various optimizations on the X protocol to make
-it faster over low bandwidth and/or high latency connections.
-
-With regard to authentication/authorization, lbxproxy simply passes
-along to the server the credentials presented by the client. Since X
-clients will connect to lbxproxy, it is important that the user's
-.Xauthority file contain entries with valid keys associated with the
-network ID of the proxy. lbxproxy does not get involved with how
-these entries are added to the .Xauthority file. The user is
-responsible for setting it up.