HISP has a shell server thats used for hosting the Subversion repositories, mailing lists and most of our services. If you are a developer on a HISP project you will get access to this machine. You are free to make your own home page and have personal Subversion repositories there.
|
You are required to change your password on the shell server as soon as possible. This is required for the safety of the server. |
After logging in to the server type:
$ passwd Changing password for trygvis (current) UNIX password: <<type your existing password>> Enter new UNIX password: <<type your new password>> Retype new UNIX password: <<type your new password again>>
Make a public folder in your home dir called public_html like this:
$ mkdir ~/public_html $ chmod a+rx ~/public_html
You should now be able to point your browser to
http://www.hisp.info/~<username>
and see a directory listing.
SSH keys are a more elegant way of using SSH. By using SSH keys you won't have to enter your password all the time while using SSH services like subversion or when logging in into the shell server.
This depends on which client you are using. Most Linux distributions comes with OpenSSH preinstalled. If you are using Cygwin you must make sure the "openssh" package is installed.
There is a common step that all clients has to do and that is to make the ~/.ssh folder on the server:
$ ssh login.hisp.info $ mkdir ~/.ssh $ chmod 755 ~/.ssh
To generate a new key pair (a public and a private part) type this on your client machine:
This will generate two files in your home directory:
Now upload the public part to the server:
The last step is to add the key to your keyring on the server:
You can have as many keys in ~/.ssh/authorized_keys as you like. If this does not work, you can try generating keys of type dsa with the following command, and then repeat the subsequent steps:
Download the putty suite![]()
Install in C:\Tools\Putty
$ssh-keygen \-b 1024 \-t dsa \-N passphrase \-f mykey
(NOTE: change passphrase to a secret keyword you only know)
$ls \-l mykey\*
You just created a SSH2 DSA key with 1024 bit key phrase. In the list you will see two files. One named "mykey" and one named "mykey.pub". As you might guess, the .pub file is the public key file, the other is the private one
Type:
$mkdir .ssh
Then go to the directory where you created your keys and copy the public key to the .ssh userfolder with the following command:
$cp mykey.pub /home/myuser/.ssh/authorized_keys
Please pay attention to the filename, it really must be "authorized_keys". In some old OpenSSH implementations, it was "authorized_keys2".
|
Check and extend these steps |
ssh.com works almost the same way as OpenSSH but they have another way of naming the files and the file formats are slightly different. You can generate the key on your client a similar command as the OpenSSH version and upload the key. Look in the ssh-keygen man page for instructions on how to convert the file to OpenSSH format.
You can log in to the shell server by using SSH to the host login.hisp.info
|
Browse Space |
Explore Confluence |
Add Content |
|
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.6 Build:#812 Aug 06, 2007) |
I cannot get SSH keys to work. I've tried both methods, and I've tried using the key of mine that works for the Department of Informatics at the University of Oslo. I'm beginning to suspect that the server is misconfigured. Has anybody been able to authenticate using keys?
(Crossposted to developer list.)