Skip to content

local ssh config (rather than remote)? #2

@hcientist

Description

@hcientist

<p> Before we add the key into our authorized key file let's ssh into stu and add some information to our ssh config. Place the following information but with your e-id

I think at the above you actually wanted to set that in your local ~/.ssh/config

this would mean that form your laptop, you'd be able to (e.g.) ssh w3 and locally, your ssh config knows that w3 refers to w3.cs.jmu.edu and that you intend to be the user e-id and that you'd like to use the listed key rather than password auth.

You may want to set something similar on the server in some cases, but this is a little unusual. If for some reason you really need to be doing some work on a particular server, and then frequently find yourself needing to then, from that remote server on which you're already working connect to another remote machine, the ssh config on the first remote would be useful

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions