Search Mailing List Archives
[farmshare-discuss] Leaving ssh-agent to run in the background?
Jaeho.Shin at Stanford.EDU
Tue Jan 13 22:45:37 PST 2015
corn.stanford.edu is an alias to a set of machines and you're not guaranteed to connect to the same one upon subsequent logins. The ssh-agent is probably running, but on a different machine than the one you logged in to the last time.
You can let your students pick their favorite number, e.g., 12, and use corn12.stanford.edu instead of the load balanced alias. This way, they will be able to always login to the same machine that has the ssh-agent process running, but may get stuck in a busy machine.
In this particular case, I think you may want to let them access GitHub via HTTPS with Personal Access Tokens. They can store their generated token in ~/.netrc and essentially have the same thing to the ssh key setup. It seems this feature isn't explicitly documented, but all you need is a line in ~/.netrc with the token generated from GitHub settings page. In fact, this may be even simpler than the ssh key setup. Here are some useful links:
> On Jan 13, 2015, at 21:49 , Dan Nguyen <dun at stanford.edu> wrote:
> I've been having my students generate a keypair on corn.stanford.edu to authenticate with their Github accounts using this process:
> The authentication process works...but after logging out and logging back in, it seems we have to manually restart the ssh-agent again and add the key to it. I'm not knowledgeable about the details of this authentication besides how it works on my own laptop, so I wanted to check if it might be just the way things are set up on afs?
> farmshare-discuss mailing list
> farmshare-discuss at lists.stanford.edu
More information about the farmshare-discuss