Closed mo-cmyk closed 1 year ago
Can you try rebooting? We've had the occasional report of the SEP stopping working for some reason https://github.com/maxgoedjen/secretive/issues/378
It seems that not the first but the second reboot solved the issue. Thanks for the help. Any idea what seems to be the reason for this bug?
Not really unfortunately - I've never had it happen on one of my personal machines - my guess is that macOS just gets into some bad state and forgets how to talk to the SEP (although I'd expect a LOT of other system level bugs in that case). Thanks for confirming that fixed it though 🙏
@maxgoedjen I have this issue relatively frequently (a couple times a month, maybe a bit more). Can we reopen this issue? I'm happy to help with debugging if you can guide me.
@c10l basically I closed this because I don't think I have any fix to the root cause – I suspect there's nothing I can do on an application-level to resolve this state (though I could be wrong there). I've opened https://github.com/maxgoedjen/secretive/issues/415 to deal with getting into this state better though.
@c10l just OOC since it's happening to you often: do you notice any other issues with your Mac when it gets into this state? I'm curious if it affects other apps, or if it's ONLY Secretive. Are you able to authenticate with Touch ID in other apps, for example?
Thanks. I haven't noticed any other impact. I can definitely use TouchID - I would have noticed that as I use it frequently on my password manager, for unlocking, etc.
I'll keep an eye out for the next time I see the issue. What other things can I check apart from TouchID?
@c10l basically the state (as near as I can tell from other descriptions) of the computer is either "the SEP doesn't respond to Secretive at all" or "the keychain APIs that we use to communicate with the SEP claim that there are no stored keys at all").
Touch ID in things like the setting page (like triggering that little lock on the Security page) would be the easiest case to verify SEP interaction is okay, for general keychain functionality, any apps that you're logged into (eg, Twitter or something), if you quit and reopen those apps, are you still logged in? That'd be a quick test.
I definitely won't rule out the possibility that I'm doing something wrong here, it's certainly possible. I'll reopen this ticket just for tracking and think of some logging changes I can make to get more info next time it happens.
I remember of at least one instance where this happened and I exported the public key from Secretive so I didn't have to reboot. Secretive asked me for TouchID to use the key and it all worked.
I suspect it's only the part where it tries to read the public keys that has a problem.
That's helpful – it implies that it's a simple keychain issue and not anything really SEP specific, or that signature request wouldn't go through.
@maxgoedjen This issue just happened to me again now. I went into System Settings and confirmed that TouchID works fine. So it does for 1Password.
Here's an interesting thing though. Public keys exported from Secretive are giving me this error:
debug2: Passphrase not found in the keychain.
Load key "/path/to/pubkey": invalid format
I copy-pasted the pub key from Secretive again just to be sure and got the same error.
Also encountered this. Key has disappeared in the GUI. Tried rebooting but to no avail.
$ echo $SSH_AUTH_SOCK
/Users/connor.edwards/Library/Containers/com.maxgoedjen.Secretive.SecretAgent/Data/socket.ssh
$ ssh-add -L
ecdsa-sha2-nistp256 (...) ecdsa-sha2-nistp256
$ ssh git@github.com
sign_and_send_pubkey: signing failed for ECDSA "ecdsa-sha2-nistp256" from agent: agent refused operation
git@github.com: Permission denied (publickey).
My Secretive App on my M1 MacBook Pro running macOS 12.4 seemed to have deleted all my SSH keys or access to those. I then wanted to recreate a Key to be able to use GitHub still, and the app quit on me after I tried to create a key; it just crashed. The Error became obvious after trying to push some code to GitHub. I tried reinstalling and using HomeBrew and the release on GitHub, but the Error persists.
This is the Debugging output provided while running
ssh -Tv git@github.com