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

Re: Commit signing with SSH key uses SSH_AUTH_SOCK but ignores IdentityAgent

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Sep 13, 2024, 15:05 UTC
Message-ID
<a25f71ad-093f-4e8d-97ef-503bfb9926d2@gmail.com>
In-Reply-To
<CAB=S_8JhN=WSuYRMWbGz7gZMRX9dSb3k8rJZ7zrxkbHKOqfzww@mail.gmail.com>
Hi Justin
On 13/09/2024 10:58, Justin Su wrote:
Show 6 quoted lines
> I use Secretive (https://github.com/maxgoedjen/secretive) to store my
> SSH keys on macOS. I've configured my ssh_config to use it as the
> IdentityAgent, and Git can push and pull just fine.
> 
> However, it seems that Git ignores IdentityAgent when signing commits,
> resulting in the following error message:

Git just runs "ssh -Y". I can reproduce this on linux - I suspect the problem is that ssh does not read the IdentityAgent config when signing even if it is outside a Host/Match in the config file.

Best Wishes
Phillip
Show 9 quoted lines
> error: No private key found for public key "foo.pub"?
> fatal: failed to write commit object
> 
> I've worked around this by setting SSH_AUTH_SOCK, but this doesn't
> feel correct to me. Is this intended behaviour?
> 
> Thanks,
> Justin
>
Previous: Justin SuNext: Justin Su
Message 2 of 3 in “Commit signing with SSH key uses SSH_AUTH_SOCK but ignores IdentityAgent”
  1. Justin SuSep 13, 2024
  2. Phillip WoodSep 13, 2024
  3. Justin SuSep 14, 2024

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.