Use of SSH Private Key Management ssh-agent

SSH Private Key Management ssh-agent use my company uses git to manage and deploy source code, so you need to bring your private key from the development machine to the Machine [plain] ssh-A xxx@192.168.0.xxx, but found to jump to the machine after the git fetch, the prompt does not find the development machine on the private key, the private key is not included. After several days of searching, it is found that the developer needs to start ssh-agent [plain] ssh-agent bash -- login-I ssh-add to encrypt and cache his private key, the ssh internal mechanism can safely bring the cached Private Key to the target machine during the communication process [ssh-agent Introduction] ssh-agent is a proxy for managing private keys, the managed private key is added through ssh-add, so clients of the ssh-agent can share these private keys. Benefit 1: You do not need to enter the password again. When you use ssh-add to add a private key, if the private key has a password, you are required to enter the password once in the example. After that, the ssh-agent can directly use the private key, no password authentication is required. Benefit 2: You do not need to deploy the private key everywhere. Assume that the private key can log on to host A and host B on the same Intranet respectively. For some reason, you cannot directly log on to host B. You can either deploy the private key on A or set PortForwarding to log on to B, or forward the Authentication Proxy connection to A and use the ssh-agent private key to log on to B.