Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move SSH instructions #12

Open
ar0r opened this issue Sep 11, 2022 · 3 comments
Open

Move SSH instructions #12

ar0r opened this issue Sep 11, 2022 · 3 comments

Comments

@ar0r
Copy link
Collaborator

ar0r commented Sep 11, 2022

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"

@ar0r
Copy link
Collaborator Author

ar0r commented Sep 11, 2022

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?

@borjasotomayor
Copy link
Member

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.

@ar0r
Copy link
Collaborator Author

ar0r commented Sep 11, 2022

We might be able to grab some text from this page: https://uchicago-capp30121-aut-2022.github.io/capp-camp/s1-linux/1-connect.html.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants