search

ebeshero / DHClass-Hub

a repository to help introduce and orient students to the GitHub collaboration environment, and to support DH classes.
GNU Affero General Public License v3.0
27 stars 27 forks source link

Problem trying to get my ssh key on my home computer #702

Closed ads171 closed 5 years ago

ads171 commented 5 years ago

Everything works fine until I reach the "ssh keygen -1" part. It says ssh protocol v.1 is no longer supported. I'm following every step to my knowledge. Sorry for the inconvenience.

Anthony

ghbondar commented 5 years ago

@ads171 It's a lowercase-L, not a one, but you can skip that step. The next step is super important: ssh-copy-id ads171@firebelly.newtfire.org

ghbondar commented 5 years ago

... of course, you would type: ssh-copy-id ads171@firebelly.newtfire.org

ghbondar commented 5 years ago

from here, you can jump into the instructions for FileZilla.

ebeshero commented 5 years ago

@ads171 Did you get it working at your house? Let us know if you're still stuck...

ads171 commented 5 years ago

I've been trying all week. It's saying i'm logged in and I have to restart my Git hub like you would on step 5 of the instructions. Even when I attempt to skip that step and go straight to ssh keygen -l it says host sever not available. This is so frustrating to me because I can't bring my home pc in like I could with a laptop. I was going to come into your office tomorrow and see what you think might be wrong. I apologize so much for this, I know I have to do this, it's just frustrating to me because I don't know what's wrong and I don't want to bother you guys 24/7 on the weekend.

From: Elisa Beshero-Bondar notifications@github.com Sent: Sunday, September 22, 2019 11:31 AM To: ebeshero/DHClass-Hub DHClass-Hub@noreply.github.com Cc: Socci, Anthony D ADS171@pitt.edu; Mention mention@noreply.github.com Subject: Re: [ebeshero/DHClass-Hub] Problem trying to get my ssh key on my home computer (#702)

@ads171https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fads171&data=02%7C01%7Cads171%40pitt.edu%7C9e05f7eb390d4e6d1e6e08d73f8b23d1%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C0%7C637047739145819163&sdata=gaaBlvWLSAsXKe1ya%2Fw5jWWHrgFcLfopvZCeH4XcRoo%3D&reserved=0 Did you get it working at your house? Let us know if you're still stuck...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Febeshero%2FDHClass-Hub%2Fissues%2F702%3Femail_source%3Dnotifications%26email_token%3DANA4Z63Z67AH5CNSQVDEVJ3QK62ZRA5CNFSM4IY35QWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7JMG3Y%23issuecomment-533906287&data=02%7C01%7Cads171%40pitt.edu%7C9e05f7eb390d4e6d1e6e08d73f8b23d1%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C0%7C637047739145829170&sdata=fQbCy%2FHG7Cfv3lCCpsiQwJEufjNPW%2B3VCTOGSMc2miU%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANA4Z656SJPKMTGQYBPB7ULQK62ZRANCNFSM4IY35QWA&data=02%7C01%7Cads171%40pitt.edu%7C9e05f7eb390d4e6d1e6e08d73f8b23d1%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C0%7C637047739145829170&sdata=pwwil4JtOu8TlMQOG%2BRAxEGBAfpVP%2F9qwpedfSREwm0%3D&reserved=0.

ghbondar commented 5 years ago

@ads171 It's no bother. Instead of the instructions on CourseWeb, just do these: 1) open a NEW Gitbash shell (close any old Gitbash windows). 2) In GitBash, type: ssh-keygen This just created a new set of keys on your computer that you are using now. 3) In GitBash, type: ssh-copy-id ads171@firebelly.newtfire.org
This will prompt you for the newtfire.org password that we have on CourseWeb. _This is copying your key (named id_rsa.pub) from your computer onto your web space._ You may close the GitBash window now, if you wish. (We should be done with it)

4) Now, open any file-folder in Windows. On the menu-bar, go to "View" -> boxes next to "Hidden items" and "File name extensions" must be checked. Close this window now, also.

5) Startup FileZilla to connect your local machine to the firebelly.newtfire.org server, first add your private key to the list of authenticated keys. To do this… a) Go to FileZilla (on menu bar) -> Edit -> Settings… b) Under Connection, click SFTP. c) Click ‘Add key file’ to browse for your private key: It will be in: C:\Users\(your username)\.ssh Click the file named id_rsa _Do NOT select idrsa.pub d) Click “OK” to save your changes.

5) Now, use FileZilla to connect to our newtfire.org web domain. In FileZilla, do this… a) Go to File --> Site Manager b) Click the New Site button, and under the “Advanced” tab, change the Server Type to Unix, and click the checkbox next to Bypass proxy c) Under the “General” tab, add firebelly.newtfire.org to the host name, and change the Protocol to SFTP d) Change the logon type to Key file, and enter your username where prompted. e) You'll need to locate your private key one more time: It will be in: C:\Users(your username).ssh and select your id_rsa key as you did before. _Do NOT select idrsa.pub f) Click connect. You can access this SFTP site connection again, and give it a name over on the left-hand panel: we named our site connection "newtfire". Now you can transfer files easily from your local computer to the remote server. ...and if you've gotten this far, you never have to do any of this again!

ebeshero commented 5 years ago

@ads171 I logged in to take a look in your directory on newtfire, and I can see that you have already put several keys on the server already. You've been generating a lot of keys, and you probably don't need to generate any more of them.

The part I think you're probably stuck on is logging in with FileZilla. Can you set up the FileZilla connection and show it where to locate your private key? If you're having trouble, remember that

(If that is not where it is, you can find out exactly where in your bash shell with cd followed by the space bar, then return. (That takes you "home".) Then type ls -lisat to see any hidden directories. You should then see .ssh and you can move in to find your private and public keys. Find the exact filepath with: pwd (which means "print working directory"): that will give the filepath to the key file.)

Tell us what happens when you do this.