-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There are usually two configs, one for the client (/etc/ssh/ssh_config) and one for the daemon (etc/ssh/sshd_config). The client config is parsed after the command line options. From my /etc/ssh/ssh_config:
# Configuration data is parsed as follows: # 1. command line options # 2. user-specific file # 3. system-wide file # Any configuration value is only changed the first time it is set. # Thus, host-specific definitions should be at the beginning of the # configuration file, and defaults at the end. You should be able to disable X11 forwarding in the sshd_config on the "server" and then the command line options from the "client" are largely irrelevant. The O'Reilly ssh book is fantastic, and I think a new edition was released in past few months. Of course you are welcome to my older edition. SSH is a swiss army knife of an application and is well worth becoming familar with. FYI, rsync + ssh is a great way to backup or replicate data, with cygwin it can even be cross platform. Shawn wrote: > I agree with the other posts that ssh as root is frowned on, and that you > should be careful with X11 forwarding. However, I think everyone missed the > real problem you are having with that command - it's not quite right. (It's > been a while since I've done this and I'm doing it from memory, so please > forgive me if I'm wrong). > > The command should be in the following format: > > ssh -X [EMAIL PROTECTED] /path/to/XApp/on/remote/computer > > So, if I wanted to run KDE's Control Center on a remote box, I would do > something like: > > ssh -X [EMAIL PROTECTED] /usr/kde/3.4/bin/kcontrol > > And if I a) have both computers running X windows, and b) have not forcibly > disabled X11 forwarding, and c) authenticate properly, then a kcontrol window > would open on the local computer, but would be affecting the remote computer > (and running as the user I authenticated as). > > I'm pretty sure that when I played with this last, my SSH configs had said > X11Forwarding=No, but it worked anyways. I think this requires a different > setting to block it outright (not allow an override at the command prompt), > or is a fluke of the network config I had at the time.... > > Hope this helps. > > Shawn > > On Monday 21 November 2005 13:05, Kin C Wong wrote: > >>Just discovered ssh last week. It is really cool. As I am not that >>comfortable using command line, I would like to run KDE. I was told >>that you could use the following command to do that: >> >>ssh -X [EMAIL PROTECTED] >> >>It doesn't seem to do anything for me. I have tried man, help and >>googling but to no avail. Any suggestions as to where to look would be >>appreciated. >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>clug-talk mailing list >>[email protected] >>http://clug.ca/mailman/listinfo/clug-talk_clug.ca >>Mailing List Guidelines (http://clug.ca/ml_guidelines.php) >>**Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDgtqVwRXgH3rKGfMRAhUvAKCbqdW8WHLuOjCvjzgQ5prSCGnckgCfWa3R r9FV/wAhzh5Qh7E8cnw3RCM= =0qTE -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
