Skip to main content
January 11, 2024
Question

SSH Key Agent no longer working after last upgrade

  • January 11, 2024
  • 3 replies
  • 204 views

I used 1Password to generate and to protect my Ed25519 key so that every time I tried logging in to my account it prompted me for Touch ID and then it would log in, after the last upgrade I can no longer log in and I'm being asked for password.

The logs show the following errors:

ERROR 2024-01-11T11:37:56.479 tokio-runtime-worker(ThreadId(10)) [1P:foundation/op-system-auth/src/auk_protect.rs:273] Failed to retrieve secret SsoUnlock from enclave EnclaveError(SecretInaccessible(Permanently))
ERROR 2024-01-11T11:37:56.479 tokio-runtime-worker(ThreadId(10)) [1P:foundation/op-system-auth/src/auk_protect.rs:273] Failed to retrieve secret WebAuthnUnlock from enclave EnclaveError(SecretInaccessible(Permanently))
ERROR 2024-01-11T11:37:56.480 tokio-runtime-worker(ThreadId(10)) [1P:op-app/src/app/backend/unlock.rs:488] NoNewAccountsUnlocked
INFO 2024-01-11T11:40:56.983 tokio-runtime-worker(ThreadId(4)) [1P:op-app/src/app/backend/frontend.rs:24] Front end event: window closed
ERROR 2024-01-11T11:40:57.080 ThreadId(15) [client:typescript] Attempted to update the window state after it was destroyed. Caused by app before-quit event.
INFO 2024-01-11T11:42:41.416 tokio-runtime-worker(ThreadId(3)) [1P:/Users/build/jsFAJPbU/0/dev/core/core/op-ui/src/edit_item/mod.rs:1411] Saving items with pre-specified UUIDs
INFO 2024-01-11T11:42:42.541 tokio-runtime-worker(ThreadId(11)) [1P:op-syncer/src/sync_job.rs:1204] pushed 1 item(s); updated: 1; failed: 0; new vault content version: 20.

It worked yesterday and now after the recent upgrade I don't see any Touch ID prompt or anything like that and I can no longer log in to anything using this key.


1Password Version: 8.10.23
Extension Version: 2.15.1
OS Version: 14.12.1
Browser: Firefox Nightly

3 replies

floris_1P
1Password Employee
1Password Employee
January 11, 2024

Thanks for adding these logs. Do you see your SSH key if you run:

SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l

If not, does it work again if you open 1Password and manually unlock the account the SSH key is in?

January 12, 2024

Hi, thank you for the rapid response, in fact ssh-add -l is working even without adding this environment variable so it's not the case.

Can I control log verbosity?

floris_1P
1Password Employee
1Password Employee
January 12, 2024

Adding the -v flag to your ssh command can be useful to see which keys are used.