My access problem is resolved - Many thanks to William Hooper In summary, the correct solution is to restrict the Xvnc -inetd access using the tcpd wrapper program in the /etc/inetd.conf with correctly configured hosts.allow and hosts.deny files. The -localhost option doesn't control this when using the -inetd option.
-----Original Message----- From: William Hooper [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 1:49 PM To: [EMAIL PROTECTED] Subject: RE: ssh tunnel problem > -----Original Message----- > From: Polak, Jon [mailto:[EMAIL PROTECTED]] > > William > > Thanks for the quick reply. > > I'm not sure I follow what you mean when you say... > > >Why not use the inetd functionality to only allow localhost > to connect (as > >suggested at http://www.dei.isep.ipp.pt/~andre/extern/ixvnc.htm )? > > I don't see anything different in their example except the > broadcast vs. > query syntax. Are you alluding to something else I may have missed? > > Thanks again > Jon > Look under the section labeled "Other Points": As pointed out by Laurent Bardi allowing or denying IP clients access it's now easy. Just check "man tcpd". You can use tcpd to control who can connect to inetd services. -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
