Max Goedjen

Hm, having trouble reproducing it here. I can repro the "locked machine failed the request" bit but on unlock and retry it works fine. ``` % sleep 30 && ssh...

> my location (and timezone). I assume this is not relevant as other folks in my organization have gone through the same process and don't get into this state. Including...

@fsouza I'd be curious if they see anything unusual/mentioning the SEP in Console.app (Secretive-related or otherwise). If there's anyone encountering this that'd be brave enough to fire up Xcode and...

Mainly I'd want to be stepping through https://github.com/maxgoedjen/secretive/blob/main/Sources/Packages/Sources/SecureEnclaveSecretKit/SecureEnclaveStore.swift#L228 and https://github.com/maxgoedjen/secretive/blob/main/Sources/Packages/Sources/SecureEnclaveSecretKit/SecureEnclaveStore.swift#L36 and also keeping an eye on the console to see if there's anything interesting.

Hm... that lines up with the other reports but doesn't give too much more additional information – basically the system just seems to be in a bad state, I'm not...

Hadn't occurred to me either, but interesting thing to try. Think the "best" solution here might be specifically watching for the interaction not allowed message and showing a "restart your...

I think this is fixed by https://github.com/maxgoedjen/secretive/pull/495 – if anyone sees it again please reopen.

This is actually a little bit of sleight of hand on Secretive's part - we're given write access to that specific file if you explicitly select it from the file...

Hey @ari-becker there's a few reasons for this right now: - The hash is the canonical unique identifier for the secret. Other fields (particularly names) do not have uniqueness constraints,...

@xrisk that was also my first reaction here – I'd suspect it's your shell prompt, not the terminal itself. I'd be curious to see if you can reproduce this in...