Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty/inaccessible SecretAgent/Data directory #486

Open
djc opened this issue Oct 6, 2023 · 7 comments
Open

Empty/inaccessible SecretAgent/Data directory #486

djc opened this issue Oct 6, 2023 · 7 comments

Comments

@djc
Copy link

djc commented Oct 6, 2023

I started looking at setting up git commit signing yesterday per the instructions in #441. However, when I look at my ~/Library/Containers/com.maxgoedjen.Secretive.SecretAgent dir using ls -l I get an error:

djc-2021 com.maxgoedjen.Secretive.SecretAgent $ ls -l
total 0
drwx------@ 14 djc  staff  448 Oct  6 10:00 Data
djc-2021 com.maxgoedjen.Secretive.SecretAgent $ cd Data 
djc-2021 Data $ sudo ls -al
total 0
ls: .: Operation not permitted

I've already tried killing the Secretive processes, but this doesn't appear to help. Adding a new key also doesn't seem to change anything.

@djc
Copy link
Author

djc commented Oct 6, 2023

(Also, this happened after creating this issue:)

Screenshot 2023-10-06 at 10 09 53

@maxgoedjen
Copy link
Owner

What version are you using? I fixed something that sounds similar to this in the last update.

@djc
Copy link
Author

djc commented Oct 9, 2023

I have "Version 2.3.1 (1.5638740552)".

@torarnv
Copy link

torarnv commented Jan 19, 2024

The reason for the ls: .: Operation not permitted is that Terminal.app (and in effect, zsh and the ls child processes) does not have access to read files of other applications. You've probably denied that permission in the past. You can reverse/change this in the system settings.

@djc
Copy link
Author

djc commented Jan 19, 2024

@torarnv thanks for the feedback, that seems to work! I wonder if there's way I can avoid granting permission to all of VS Code and still use this with git in VS Code's Terminal tabs...

@torarnv
Copy link

torarnv commented Jan 19, 2024

A solution like outlined in #499 (comment) would help with that.

@djc
Copy link
Author

djc commented Jan 22, 2024

I think we would also need to write the socket.ssh value somewhere else, probably, to make that feasible? Presumably the git process would need access to the inode referred to by the socket.ssh name in SecretAgent/Data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants