Signing back into the Community for the first time? You'll need to reset your password to access your account.  Find out more.

Forum Discussion

Former Member's avatar
Former Member
3 years ago

upgraded to git 2.40.0 on homebrew and 1Password quit signing, throws error

➜ .brew-file git:(main) ✗ git commit -a -m "update"
error: error: Found argument '-U' which wasn't expected, or isn't valid in this context

If you tried to supply `-U` as a value rather than a flag, use `-- -U`

USAGE:
op-ssh-sign [OPTIONS] -Y [--] [payload]

For more information try --help

fatal: failed to write commit object

NOTE: if i remove git from homebrew and use the Apple supplied git, it all works. But this means i'm running an older version of git for everything...

1Password Version: 1Password for Mac 8.10.1 (81001033)
Extension Version: 2.8.1
OS Version: macOS Ventura 13.2.1
Browser:_ Chrome 111.0.5563.64 (Official Build) (arm64)
Referrer: forum-search:git 2.40.0

SSH
  • Former Member's avatar
    Former Member
    2 years ago

    Indeed, we have released a fix for this both on the production and on the nightly channels.

  • scottaw's avatar
    scottaw
    Occasional Contributor
    2 years ago

    Yep, thanks for the super fast turnaround on this one.

  • scotte_zinn's avatar
    scotte_zinn
    New Contributor
    2 years ago

    Works for me as well - kudos to the support and dev team on a quick turnaround! Thanks all

  • Former Member's avatar
    Former Member
    2 years ago

    awesome, just updated 1Password and reinstalled git 2.40.0 via brew, it seems to be working again... Thank you !!

  • hughbiquitous's avatar
    hughbiquitous
    New Contributor
    3 years ago

    floris_1P I already have SSH_AUTH_SOCK set to $HOME/.1password/agent.sock, so I just commented out the [gpg "ssh"] section from my .gitconfig and everything worked just fine.

    This makes me wonder -- is the [gpg "ssh"] section even necessary if SSH_AUTH_SOCK is already set? Put another way, is op-ssh-sign doing anything that I don't already get by having SSH_AUTH_SOCK set up?

  • Former Member's avatar
    Former Member
    3 years ago

    We have a fix for it ready, which will become available later today.

    I can certainly wait until later today!

    (But for what it's worth, git config --show-origin --get-all gpg.ssh.program returns no output. I don't think that it is mentioned in the docs for using op with ssh and git.)

  • floris_1P's avatar
    floris_1P
    Icon for 1Password Team rank1Password Team
    3 years ago

    You can run git config --show-origin --get-all gpg.ssh.program to see where op-ssh-sign gets set. Make sure comment out or remove that line. Alternatively, if it's easier, you can also consider downgrading Git.

    We have a fix for it ready, which will become available later today.

  • Former Member's avatar
    Former Member
    3 years ago

    I'm also having problems getting this to work.

    I note that I don't have gpg.ssh.program in .gitconfig. Rather, I have
    IdentityAgent "~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock"
    in .ssh/config.

    I wonder if I need to reboot or at least log out/in?