convore.json/groups/git/how-to-get-git-remote-operations-to-store-key-in-ssh-agent/messages.json

[{"user_id": 14411, "stars": [], "topic_id": 21388, "date_created": 1303817031.4560211, "message": "I had the following question on AskUbuntu http://askubuntu.com/questions/36255/why-wont-ssh-agent-save-my-unencrypted-key-for-later-use and I wonder if there is some way to get it to only request the passphrase for my key when I perform a remote operation.", "group_id": 106, "id": 812624}, {"user_id": 2142, "stars": [], "topic_id": 21388, "date_created": 1303821667.831593, "message": "I'm not sure to understand your problem correctly", "group_id": 106, "id": 813265}, {"user_id": 2142, "stars": [], "topic_id": 21388, "date_created": 1303821740.6904869, "message": "in ~/.ssh/config add:\nHost *\n  ForwardAgent yes", "group_id": 106, "id": 813286}, {"user_id": 2142, "stars": [], "topic_id": 21388, "date_created": 1303821711.6936591, "message": "If you want to ssh from A->B->C, you can enable the ForwardAgent option which gives access to your ssh-agent on A from B and C, but it has some security implication if B or C are compromised `man ssh_config`", "group_id": 106, "id": 813273}, {"user_id": 2142, "stars": [], "topic_id": 21388, "date_created": 1303822124.651017, "message": "ssh will discuss with ssh-agent trough a socket specified by the SSH_AUTH_SOCK environment variable. if you want to avoid having N ssh-agent on the same machine, you could imagine storing that variable in ~/.ssh/agent.env to share it with the other bash sessions", "group_id": 106, "id": 813383}, {"user_id": 28370, "stars": [], "topic_id": 21388, "date_created": 1303860827.974, "message": "Enabling agent forwarding for every connection is usually not a good idea.  Selectively enable it only for the servers you want to use it with.", "group_id": 106, "id": 819979}, {"user_id": 14411, "stars": [], "topic_id": 21388, "date_created": 1303891392.3029759, "message": "Its not agent forwarding. Although in hindsight that is probably a neater way to achieve this given my work flow. It looks likely that an ssh wrapper script is the only other way to do it. http://stackoverflow.com/questions/5789729/how-to-get-only-remote-git-operations-to-trigger-a-ssh-add-event-for-ssh-agent/5793263#5793263", "group_id": 106, "id": 823232}]