-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Most default installs disable direct root access. You can change this in /etc/ssh/sshd_config by changing PermitRootLogin to yes.
A better option is ssh in as a regular user, and use sudo (or su) to run commands as root. Mitchell Brown wrote: > One quick question: Why can't I login as root? It keeps saying my password > is bad. Which it's not. > > On 4/23/06, Shawn <[EMAIL PROTECTED]> wrote: >> On Sunday 23 April 2006 13:40, Mitchell Brown wrote: >>> Hi, >>> I can already remotely administer my Linux box via VNC - I'm wondering >> how >>> I can do the same thing, without a graphical interface. Basically, a >> remote >>> terminal. >>> I think this is called SSH but I am not sure. >>> >>> Can someone give me (in English) steps on how to set this up? >> On the Linux box you want to control, make sure OpenSSH is installed and >> running. TAKE THE TIME TO DO THIS RIGHT - lock it down to allow only the >> access you want. Make sure your user accounts have strong passwords. >> >> On the box you are going to be connecting FROM, make sure you have OpenSSH >> installed (though the service doesn't neccesarily need to be running >> there). >> If you are connecting from a Windows box, use the program called >> PuTTy. The >> interface is pretty straight forward to use. >> >> >From a Linux box, go to a command prompt, and type in the following: >> >> ssh [EMAIL PROTECTED] >> >> The "myusername" part would be a valid username on the remote box. The >> "remotecomputername" part would be the name or IP address of the remote >> box. >> (make sure the name can be resolved to an IP). >> >> You will then be prompted with some warnings. Say that yes you want to >> accept >> the connection info for the remote box (don't remember the exact wording >> of >> this) - this will only happen once, the next time it will use the stored >> info. Then you'll be prompted for the password of the remote user. >> >> If all goes well, you will now have a command prompt FOR THE REMOTE >> BOX. If >> you were to enter the 'halt' command, the remote server would shut down >> (if >> the user had permission to enter that command). There is absolutly no >> difference between this command prompt and sitting at the remote computer >> logged in to a local shell. (well, yeah there are some differences, but >> you >> get the idea...) When you logout of that command prompt, you will return >> to >> your local prompt. >> >> Once you have this set up, you can begin to explore the more advanced >> things >> you can do with ssh - like setting up trusted keys to allow authorized >> computers to connect without a password prompt, or running a KDE >> application >> on the remote computer showing it's output to your local computer - >> without >> having to get a full screen dump (like VNC). Or use SCP or SFTP to >> transfer >> files. >> >> HTH. >> >> Shawn >> >> >> _______________________________________________ >> 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 >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFES+wtwRXgH3rKGfMRAue3AJ9Ruob19UX+yB8rPUl3NE/johXOkgCfZglV Bc1C/PD5tQ2NebUH0sQF7ps= =aUVL -----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
