Github Generating Ssh Key No Such File Or Directory

/ Comments off

4.3 Git on the Server - Generating Your SSH Public Key. Generating Your SSH Public Key. That being said, many Git servers authenticate using SSH public keys. In order to provide a public key, each user in your system must generate one if they don’t already have one. Oct 17, 2017 Dismiss Join GitHub today. GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Ssh

Already on GitHub? Sign in to your account

Labels
Key

Comments

commented Aug 26, 2017•

Hi Team!

I faced with error
* stat : no such file or directory
when empty file was provided as source file to be uploaded to AWS instance.

Terraform Version

Issue explanation

Terraform failed during AWS instance creation when chef server key was replaced with empty file
(it is not usual use case, just human mistake but anyway it should not failed instance creation)

Code snippet:

When file '${var.chef_key}' is empty instance creation fails with error:

Workaround:

echo 'some-data-i-do-not-need' > /path/to/source/file

Expected Behavior

Instance is created with empty file

Actual Behavior

Instance creation failed with error:

References

Looks like very close to this issue:
#10531

added bugprovisioner/file labels Aug 28, 2017

commented Feb 13, 2019

It would be great if this error message could just be changed to:

And super great if the error message could refer to the resource and provisioner involved (perhaps by line number since provisioners don't have names).

Closed
added v0.10v0.11 labels Aug 29, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-07-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise.For help with the upgrade, contact GitHub Enterprise support.

Github Generating Ssh Key No Such File Or Directory Online

After you've checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.

If you don't already have an SSH key, you must generate a new SSH key. If you're unsure whether you already have an SSH key, check for existing keys.

If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.

Github Generating Ssh Key No Such File Or Directory Download

Generating a new SSH key

  1. Open TerminalTerminalGit Bashthe terminal.

  2. Paste the text below, substituting in your GitHub Enterprise email address.

    This creates a new ssh key, using the provided email as a label.

  3. When you're prompted to 'Enter a file in which to save the key,' press Enter. This accepts the default file location.

  4. At the prompt, type a secure passphrase. For more information, see 'Working with SSH key passphrases'.

Adding your SSH key to the ssh-agent

Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. When adding your SSH key to the agent, use the default macOS ssh-add command, and not an application installed by macports, homebrew, or some other external source.

  1. Start the ssh-agent in the background.

  2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your ~/.ssh/config file to automatically load keys into the ssh-agent and store passphrases in your keychain.

  3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

    Note: The -K option is Apple's standard version of ssh-add, which stores the passphrase in your keychain for you when you add an ssh key to the ssh-agent.

    If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see 'Error: ssh-add: illegal option -- K.'

  4. Add the SSH key to your GitHub account.

If you have GitHub Desktop installed, you can use it to clone repositories and not deal with SSH keys. It also comes with the Git Bash tool, which is the preferred way of running git commands on Windows.

  1. Ensure the ssh-agent is running:

    • If you are using the Git Shell that's installed with GitHub Desktop, the ssh-agent should be running.

    • If you are using another terminal prompt, such as Git for Windows, you can use the 'Auto-launching the ssh-agent' instructions in 'Working with SSH key passphrases', or start it manually:

  2. Add your SSH private key to the ssh-agent. https://basketyellow585.weebly.com/blog/samsung-c480fw-driver-mac-download. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

  3. Add the SSH key to your GitHub account.

  1. Start the ssh-agent in the background.

  2. Add your SSH private key to the ssh-agent. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

  3. Add the SSH key to your GitHub account.

  1. Start the ssh-agent in the background.

  2. Add your SSH private key to the ssh-agent. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

  3. Add the SSH key to your GitHub account.

Further reading

  • 'About SSH'
  • 'Working with SSH key passphrases'