On Tue, Apr 23, 2002 at 11:38:26AM +0200, Neil Blakey-Milner wrote:
> There are people who will tell people that still use X11 tcp sockets to
> start living in the 21st century. ssh X11 forwarding still works, it's
> only the (often much lower security) tcp sockets that are disabled by
> default. (And if the "none" cipher is available, the overhead would be
> minimal for even the most underpowered machine.)
I may not understand all the issues here, but can the situation be
helped by improving the reporting. I.e. if the firewalling prohibits
access to the X11 TCP socket, why would the firewall not report this
instantly at the first attempt to connect, to be visible at the console
and in /var/log/messages. I am sure Greg would have caught that first
time around, and it would have safed him from a few hours of useless
debugging time.
Joerg
--
Joerg B. Micheel Email: <[EMAIL PROTECTED]>
WAND and NLANR MOAT Email: <[EMAIL PROTECTED]>
The University of Waikato, CompScience Phone: +64 7 8384794
Private Bag 3105 Fax: +64 7 8585095
Hamilton, New Zealand Plan: PMA, TINE and the DAG's
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
