From: rich@example.invalid   
      
   Harold Johanssen  wrote:   
   > On Mon, 24 Oct 2022 13:38:27 -0000 (UTC), Lew Pitcher wrote:   
   >   
   >> On Mon, 24 Oct 2022 05:42:30 +0000, Henrik Carlqvist wrote:   
   >>   
   >>> On Sun, 23 Oct 2022 15:23:40 +0000, Lew Pitcher wrote:   
   >>>> This implies that the vncserver X server /does not/ use TCP to   
   >>>> converse with X clients, but instead uses the X "Local" support   
   >>>> (shared memory, unix socket, etc). So, nothing is listening for the   
   >>>> traffic made "local"   
   >>>> to localhost.localnet by ssh X11Forwarding.   
   >>>   
   >>> Ouch. Well, if so, maybe that problem can be circumvented with   
   >>> something like Xnest or Xephyr running on host A.   
   >>   
   >> Or, apparently, recompiling the vncserver X server to include TCP/IP   
   >> support :-)   
   >   
   >        Actually, I have just been informed that that's not necessary:   
   > it's just a matter of editing /etc/tigervnc/vncserver-config-defaults and   
   > adding the line   
   >   
   >        listen=tcp   
   >   
   > which I have experimentally confirmed to be correct. It would be nice if   
   > this could be documented more prominently (or at all) but, at the very   
   > least, the capability is there.   
      
   Often, with open source programs, changes like this are the result of   
   users letting the developers know of the hole so it can be patched.   
      
   You might consider reporting a "documentation enhancement" item on   
   whatever issue tracker they use.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)