On 9/25/05, Ralph Shumaker <[EMAIL PROTECTED]> wrote: > The last sentence is somewhat unclear to me. Is 'ssh > [EMAIL PROTECTED]' (also unclear to me) to be done on the > receiving computer or on mine?
On yours. There are two programs. One is called "ssh" and that's the client, i.e. the one you would use. The other program is called "sshd" and that's the server. Start the server on her computer. With her "sshd" server running, you use "ssh" to establish a connection. You need to know two things to do that: 1) your login name on her computer, and 2) what her computer is called. On your computer you'd say, on the command line, "ssh [EMAIL PROTECTED]", assuming your login on her computer was "login", and assuming that her computer is called "hercomputer". To get into my girlfriend's computer, for example, I would type "ssh [EMAIL PROTECTED]". My login name is "todd", and her computer is called "snake.dyndns.org"[1]. An initial hump to get over is naming her computer. You have to know what her computer is called. One way to accomplish this is to set her up with DynDNS or some like service. This will allow her to associate her IP address with a domain name, so that you can reference the domain name as her computer's name. That's what has happened in my example above. My girlfriend registered an account with DynDNS, and when she tells DynDNS her IP address, then DynDNS sends all requests for "snake.dyndns.org" to that IP address. A simpler way of doing it (maybe) is simply to use her IP address. In this case you'd use a command like "ssh [EMAIL PROTECTED]", if 69.239.117.25 were her IP address. The IP address will be different every time she gets online. A way to find out what it is is to have her go to http://whatismyip.com/ . Try it yourself right now. That tells you what IP address you are visiting the website from, i.e. that is your IP. When she goes to that website she'll see *her* IP. Then she can either call you and tell you it, or send you an email with it. (There's no security risk with sending it through the email.) Once ssh, your client, establishes a connection with sshd, her server, it will ask you for your password to get on to her computer. Give it the password and you're in. It will give you a command line for her computer. It will be just as if you were physically sitting at her computer and using the command line. You can do all the things that you are normally allowed to do on her command line. You say you have root privileges on her computer. You can "su -", no problem. You can "lsusb" or "yum" or whatever. If you want to run X (GUI) programs, you can do that, too, but it takes some extra set up involving a "ForwardX11" variable. Then, any X programs you start on her computer ("gtkpod", for example) will appear on your computer, assuming you have X running. I've never done this myself, so I can't tell you anything more about it. I would think, however, that running all that GUI data back and forth over a dialup connection would be a bit painful. > Something I wish man pages would do is > give more examples and explain what the examples do. It usually > explains things in such a seemingly cryptic way. I second that sentiment. > "man ssh" works on mine. Doesn't that mean I have it already? Yes. -todd -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
