You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like 141 is going to use individual hosted VMs instead of the general Linux servers. For that reason and because we might as well teach the students how to set up ssh keys to use with the Linux servers on their home machines, I suggest we add a new section on setting up SSH keys. We can move the ssh key generation instructions out of the Git tutorial and add text to explain how to copy the key over to the linux servers. I think something like this will work on MacOS, Windows, and Linux machines:
This issue is either not urgent or is a non-issue. Aaron and I had a misunderstanding. The students will use CNetIDs and passwords for the individual VMs.
@borjasotomayor Do you know what Colin's take is on using SSH keys rather than passwords to access department servers?
I don't think Techstaff has a preference on this, although SSH keys are generally safer. I think it's still worth adding a section on "How to create an SSH key on your own system", since that is something students will likely end up doing at some point.
It looks like 141 is going to use individual hosted VMs instead of the general Linux servers. For that reason and because we might as well teach the students how to set up ssh keys to use with the Linux servers on their home machines, I suggest we add a new section on setting up SSH keys. We can move the ssh key generation instructions out of the Git tutorial and add text to explain how to copy the key over to the linux servers. I think something like this will work on MacOS, Windows, and Linux machines:
cat ~/.ssh/id_rsa.pub | ssh amr@linux.cs.uchicago.edu "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"
The text was updated successfully, but these errors were encountered: