Not necessarily - ssh often also compresses data, which means you may very well get equal or better throughput through a secure connection.
---------------------------------------------------------------------- Andrew J Perrin - Ph.D. Candidate, UC Berkeley, Dept. of Sociology Chapel Hill, North Carolina, USA - http://demog.berkeley.edu/~aperrin [EMAIL PROTECTED] - [EMAIL PROTECTED] On Thu, 22 Feb 2001, Vadim A Kutsyy wrote: > But faster, right? > > > On Thu, 22 Feb 2001, Andrew Perrin wrote: > > > Well, not exactly 'forwarding' - setting DISPLAY that way will simply make > > the remote machine display to your X server; it's not forwarded, just > > directly displayed. And you're correct - it's not secure. > > > > ---------------------------------------------------------------------- > > Andrew J Perrin - Ph.D. Candidate, UC Berkeley, Dept. of Sociology > > Chapel Hill, North Carolina, USA - http://demog.berkeley.edu/~aperrin > > [EMAIL PROTECTED] - [EMAIL PROTECTED] > > On Thu, 22 Feb 2001, Vadim Kutsyy wrote: > > > > > Joseph Dane wrote: > > > > local> ssh -X remote > > > > remote> DISPLAY="" xlogo > > > > If you cleared the DISPLAY variable the client ('xlogo', in this case) > > > > won't know how to contact the X server. > > > > > > Correct me if I am wrong, but setting DISPLAY=your.computer.ip:0.0 will > > > create non secure X forwarding, which is a little bit faster. I am > > > aware of a few ssh servers which don't alow ssh display forwarding. So > > > the only way there is via regular forwarding. > > > > > > > > > -- > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > > > > > ---------------------------------- > Vadim Kutsyy > [EMAIL PROTECTED] > http://www.umich.edu/~kutsyy > >