ssh-keys
Saving ssh key fails
If you’re using Windows, the unix-style default path of ssh-keygen is at fault. In Line 2 it says Enter file in which to save the key (/c/Users/Eva/.ssh/id_rsa):. That full filename in the parantheses is the default, obviously Windows cannot access a file like that. If you type the Windows equivalent (c:\Users\Eva\.ssh\id_rsa), it should work. Before …
SSH agent forwarding during docker build
For Docker 18.09 and newer You can use new features of Docker to forward your existing SSH agent connection or a key to the builder. This enables for example to clone your private repositories during build. Steps: First set environment variable to use new BuildKit export DOCKER_BUILDKIT=1 Then create Dockerfile with new (experimental) syntax: # …
I’ve already setup the ssh key, but VSCode keeps asking for password
It was a problem with the config file. The VSCode needs the “absolute” path. In case of MacOS, ssh-copy-id seems to only copy the absolute path relative to the user. In other words, it omits “/Users/username” before “/.ssh“. Adding “/Users/username” in the IdentityFile attribute in .ssh/config solved the problem.
Pulling from Git fails and gives me following error: client_global_hostkeys_private_confirm: server gave bad signature for RSA key 0
The message “client_global_hostkeys_private_confirm: server gave bad signature for RSA key 0” is not an error, it is a warning, and it is related to some ssh versioning issue. It used to be very common to receive from GitLab. If you want it to go away, you can make sure that your ~/.ssh/config contains the following: …
unable to get SSH keys working between sourcetree and github
In order to get it worked I ended up going to Tools -> Options -> SSH Client and changing it to OpenSSH. I generated and uploaded several different types of keys trying to get it work as well but I think this is what finally did it.
ssh-agent and crontab — is there a good way to get these to meet?
In addition… If your key have a passhphrase, keychain will ask you once (valid until you reboot the machine or kill the ssh-agent). keychain is what you need! Just install it and add the follow code in your .bash_profile: keychain ~/.ssh/id_dsa So use the code below in your script to load the ssh-agent environment variables: …
Error connecting to agent: no such file or directory – adding key to ssh agent [closed]
VonC is probably right, in that you need to fix your path, but I was facing the same problem despite using the correct one. In my case, I needed to start ssh-agent for the command to work. Running the sample commands from GitHub was not working, but, since I had installed OpenSSH, I simply started …
How to generate ssh keys (for github)
The command to run is only ssh-keygen -t rsa -C “you@example.com” All the rest beginning with line 2 of your script is the output of ssh-keygen. And replace you@example.com with your email address. Have a look at the manual for ssh-keygen to look for additional options. You should probably use a longer key by adding …