home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.slackware      I think its the one without Selinux crap      87,272 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 86,033 of 87,272   
   Lew Pitcher to Henrik Carlqvist   
   Re: xhost not working under TigerVNC   
   23 Oct 22 15:23:40   
   
   From: lew.pitcher@digitalfreehold.ca   
      
   On Sun, 23 Oct 2022 14:35:45 +0000, Henrik Carlqvist wrote:   
      
   > On Sun, 23 Oct 2022 14:07:55 +0000, Lew Pitcher wrote:   
   >> That means that vncserver must use an X11 "Local" connection to service   
   >> that part of the interaction. "Local" connections are often implemented   
   >> as a Unix-domain socket (akin to a pipe), and not a network connection.   
   >>   
   >> This means that ssh X11 forwarding (which works by making the remote   
   >> server look like it exists on the X11 client system localhost.localnet)   
   >> won't work here.   
   >   
   > Why not? Ssh X11 forwarding will accept X traffic on something like   
   > localhost:11 on machine B where the sshd process accepts tcp connections   
   > to port localhost:6011. That traffic will then be forwarded through the   
   > ssh tunnel where the ssh process connects to DISPLAY :1 om machine A.   
      
   The X11Forwarding option transfers TCP port 6000 traffic from one end   
   of the ssh connection to the other. On the OP's system A, he needs an   
   X server that listens on TCP port 6000 to accept that forwarded traffic.   
   (X11Forwarding is helpful when your X server only accepts TCP connections   
   from localhost.localnet, and unnecessary if your X server accepts TCP   
   connections from other network addresses).   
      
   However, from the ss(1) dump the OP provided, the OP's X server (vncserver)   
   does not appear to accept traffic on port 6000, and only has open the   
   VNC protocol ports necessary to converse in VNC protocol with the vncviewer.   
      
   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.   
      
      
   At least, that's how it appears to me. Agreed that the OP's problem   
   is moderately complex, and I may have missed something or misunderstood   
   the configuration or problem.   
      
   >   
   > regards Henrik   
      
   Regards, likewise   
   --   
   Lew Pitcher   
   "In Skills, We Trust"   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca