Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
3 years agoupgraded 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
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:https://1password.community/search?Search=git%202.40.0
19 Replies
- Former Member
Indeed, we have released a fix for this both on the production and on the nightly channels.
- scottawOccasional Contributor
Yep, thanks for the super fast turnaround on this one.
- scotte_zinnNew Contributor
Works for me as well - kudos to the support and dev team on a quick turnaround! Thanks all
- Former Member
awesome, just updated 1Password and reinstalled git 2.40.0 via brew, it seems to be working again... Thank you !!
- Former Member
It's already out for macOS:
https://releases.1password.com/mac/8.10/#changelogWorking for me with the original git config back in place and no extra env vars.
floris_1P Thank you 🫡
- Former Member
floris_1P How's that fix going? :)
- hughbiquitousNew Contributor
floris_1P I already have
SSH_AUTH_SOCKset to$HOME/.1password/agent.sock, so I just commented out the[gpg "ssh"]section from my.gitconfigand everything worked just fine.This makes me wonder -- is the
[gpg "ssh"]section even necessary ifSSH_AUTH_SOCKis already set? Put another way, isop-ssh-signdoing anything that I don't already get by havingSSH_AUTH_SOCKset up? - Former Member
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.programreturns no output. I don't think that it is mentioned in the docs for usingopwithsshandgit.) - floris_1P
1Password Team
You can run
git config --show-origin --get-all gpg.ssh.programto see whereop-ssh-signgets 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
I'm also having problems getting this to work.
I note that I don't have
gpg.ssh.programin.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?