If your git.uio.no isn't working yet

If you have not yet been able to get the GIT UIO up and running, I think it may be best that you use Github for your first assignment. It's a bit easier for you to upload keys yourself and get it working. The following is only for those who do not have git.uio.no set up yet. Those who have git.uio.no working should ignore this message.

You can reuse the same key for github and git.uio.no and any other ssh connection you want to authenticate towards. Don't regenerate keys if you already have UIO git working or you have submitted your keys to me. (Some late submitted keys are still waiting to be added)

So, if you haven't yet generated an ssh key, run "ssh-keygen -t rsa -b 4096" in your home directory, for example in your UIO linux account. This generates an id_rsa and id_rsa.pub file in your .ssh directory, overwriting your old ones (hence don't do it if you've submitted keys to me). These files can be copied between computers so you can use the same key to log in from different computers, but be careful not to send the file in an insecure manner such as email.

More info on github ssh here: https://help.github.com/articles/generating-ssh-keys When using github, you need to create a github account and upload your ssh public key part. The key length in these instructions is different, but this shouldn't really matter. Use the longer key length for higher security.

When you have github up and running for assignment 1, by the end of the assignment (Sunday this week), email the public key to your group teacher. Copy your public key to a file <uio-user-id>.pub before you email it to your group teacher. Do not send your key to your group teacher if you have a working git.uio.no account already.