From 08196fb2414c31d471c2580582dcaba0bbee1f4d Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Wed, 18 May 2011 12:08:25 -0400 Subject: [PATCH] Gentler lead in in mxconns post. --- posts/mxconns.mdwn | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/posts/mxconns.mdwn b/posts/mxconns.mdwn index ebcb987..efbbb75 100644 --- a/posts/mxconns.mdwn +++ b/posts/mxconns.mdwn @@ -3,16 +3,16 @@ [Lionel Cons][LC]'s [mxconns][] is an X Windows monitor and proxy. The author suggests you use it to enhance the security of your X server by monitoring for connection attempts and dangerous requests -(e.g. keylogging). - -I ran into it while trying to get X forwarding working with my -[[cluster|Abax]]. Ususally if you [[SSH]] into a remote computer and -want to run X applications, you use `ssh -Y` to forward your X -connection to the remote host, and everything works as expected. -However, I could not figure out how to expose the forwarded server so -it could except connections from other nodes in the cluster. For -example, if a job I had running on `n1` wanted to talk to my X server -(e.g. via [[MPE]]), it would need to connect to `n0`: +(e.g. keylogging). I tend to use it as a flexible proxy fo X +forwarding with my [[cluster|Abax]]. + +Ususally if you [[SSH]] into a remote computer and want to run X +applications, you use `ssh -Y` to forward your X connection to the +remote host, and everything works as expected. However, I could not +figure out how to expose the forwarded server so it could except +connections from other nodes in the cluster. For example, if a job I +had running on `n1` wanted to talk to my X server (e.g. via [[MPE]]), +it would need to connect to `n0`: home <--(ssh -Y)----> n0 <--(???)----> n* -- 2.26.2