git/list[1] front-page[2] threads[3] people[4] search[5] about
 

SSH key errors

From
CACuckoo Aidan <aidancuckoo@gmail.com>
Date
Sep 20, 2022, 05:17 UTC
Message-ID
<CACNTUeYfOXwF+WWAi=EVLw3snkAFtAoDkBK_YZG6AxVvPAHDQg@mail.gmail.com>

Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

I added an SSH key to Git using a guide from GitHub (https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key#telling-git-about-your-ssh-key)

What did you expect to happen? (Expected behavior)
It would sign my commits.
What happened instead? (Actual behavior)
It throws an error:
error: Load key "blah blah blah" invalid format?
fatal: failed to write commit object
What's different between what you expected and what actually happened?
Commits should work, not fail.

[System Info] git version: git version 2.37.3 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:25:27 PDT 2022; root:xnu-8020.141.5~2/RELEASE_X86_64 x86_64 compiler info: clang: 13.1.6 (clang-1316.0.21.2.5) libc info: no libc information available $SHELL (typically, interactive shell): /bin/zsh

Message 1 of 1 in “SSH key errors”
  1. Cuckoo AidanSep 20, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.