>> I beleive so. If you choose to forward X into your internal LAN, you can't
>> also remotely display X windows nto the firewall too.
>
>Not quite, the X protocol allows for a number of displays on a single
>machine, numbered form 1-10 and listening on ports 6001-6010 the export
>syntax being: export DISPLAY=<my.ip.address>;0-10. You will have to find
>out what the syntax on the X server is to force it to listen to a
>different port on the linux machine.
Are you sure about this? If a user forwards say ports 6000-6010, you
can still remotely display X windows on both the firewall and the internal
machine? I don't beleive remote X displays (say :0, :1, :2, etc map
one for one to ports 6000, 6001, 6002, etc.
>Neither would I but he said that he had an X server running on NT (which
>I'm not sure if there is an X forwarding implmentation of ssh for) already
>so I assumed he had met and dealt with the security issues already.
SecureCRT from www.vandyke.com supports port forwarding for both Win9x
and NT. I also beleive a few other SSH implimentations for Win32
will do this too.
--David
.----------------------------------------------------------------------------.
| David A. Ranch - Linux/Networking/PC hardware [EMAIL PROTECTED] |
!---- ----!
`----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
