Skip to content
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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

OpenSSH-generated private keys do not work in App CR #137

Open
bcdurden opened this issue Feb 24, 2022 · 3 comments
Open

OpenSSH-generated private keys do not work in App CR #137

bcdurden opened this issue Feb 24, 2022 · 3 comments
Labels
carvel-accepted This issue should be considered for future work and that the triage process has been completed good first issue An issue that will be a good candidate for a new contributor priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@bcdurden
Copy link

When creating an App object using a ssh-git source and ssh private key, if the key was generated using openssh (default on MacOS as of this date) then it will fail complaining of key formatting.

usefulErrorMessage: "Error: Syncing directory '0': Syncing directory '.' with git
    contents: Fetching git repository: Git [fetch origin]: exit status 128 (stderr:
    Failed to add the host to the list of known hosts (/home/kapp-controller/.ssh/known_hosts).\r\nLoad
    key \"/etc/kappctrl-mem-tmp/kapp-controller-fetch-template-deploy420243064/.vendir-tmp/incoming/git-auth/private-key\":
    invalid format\r\[email protected]: Permission denied (publickey).\r\nfatal: Could
    not read from remote repository.\n\nPlease make sure you have the correct access
    rights\nand the repository exists.\n)\n"
@bcdurden bcdurden added the carvel-triage This issue has not yet been reviewed for validity label Feb 24, 2022
@benmoss
Copy link
Contributor

benmoss commented Feb 24, 2022 •
edited
Loading

What are the headers of your private key? Like -----BEGIN OPENSSH PRIVATE KEY----- or what?

A repro of this would be helpful.

@benmoss
Copy link
Contributor

benmoss commented Feb 24, 2022

Ah, I see the thread on Slack mentions that it is -----BEGIN OPENSSH PRIVATE KEY----- and that appears to be the problem

@bcdurden
Copy link
Author

Yes, sorry I should have been more specific. That header is specifically what triggers it I believe. When I switched to something with -----BEGIN RSA PRIVATE KEY----- it worked

@joe-kimmel-vmw joe-kimmel-vmw added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. good first issue An issue that will be a good candidate for a new contributor and removed carvel-triage This issue has not yet been reviewed for validity labels Feb 25, 2022
@aaronshurley aaronshurley moved this to To Triage in Carvel Jul 26, 2022
@github-project-automation github-project-automation bot moved this to To Triage in Carvel Feb 14, 2023
@neil-hickey neil-hickey added the carvel-accepted This issue should be considered for future work and that the triage process has been completed label Feb 22, 2023
@neil-hickey neil-hickey moved this from To Triage to Unprioritized in Carvel Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
carvel-accepted This issue should be considered for future work and that the triage process has been completed good first issue An issue that will be a good candidate for a new contributor priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
Carvel
Status: Unprioritized
Milestone
No milestone
Development

No branches or pull requests
4 participants
@benmoss @neil-hickey @bcdurden @joe-kimmel-vmw