Now the question: It seems like the command ssh-agent does not set the environment variables, but only returns them as a command string that must be evaluated (I'm curious as to why it works this way). The login is interactive and your command is passed as if you typed it on the interactive command line. If I want to start ssh-agent in a new shell I can run ssh-agent /bin/bash rather than starting the shell, and then repeating the previous command (I know that the new shell can inherent ssh-agent from the parent shell, but I'm just interested in understanding what is going on with this command) $ ssh-agent /bin/bash More easily I can just use eval $ eval $(ssh-agent) Identity added: /home/username/.ssh/id_rsa (/home/username/.ssh/id_rsa)
Linux start ssh shell install#
Install an OpenSSH compatible SSH client if one is not already present. $ SSH_AUTH_SOCK=/tmp/ssh-grVAkSC9cY98/agent.18454Įnter passphrase for /home/username/.ssh/id_rsa: See the Remote Development with Linux article for information prerequisites and. SSH_AGENT_PID=18455 export SSH_AGENT_PID Note that you wont be able to exit to your default shell, it will just close the connection. SSH_AUTH_SOCK=/tmp/ssh-grVAkSC9cY98/agent.18454 export SSH_AUTH_SOCK Go to Connection > SSH and set the Remote command to bash. If I want to start ssh-agent in the current shell, I can run the agent, and then manually set the environment variables that the agent returns.
In each new shell I confirm that ssh-agent is not running.
Open a terminal (for Linux) or a command line (. Note that for each example I close my session, and then start out with a fresh bash shell. Open the list of your servers and click on the one you need. Below are three samples of how I have run ssh-agent. I am just trying to better understand running ssh-agent. For information about running commands on your Windows instance at launch, see Run commands on your Windows instance at launch and Manage Windows instance configuration in the Amazon EC2 User Guide for Windows Instances.
0 kommentar(er)
