user doesn't have read access to /keybase/private/scripts

[dschneiderch]

I am constantly getting nagged about dschneiderch does not have read access to /keybase/private/scripts and also /keybase/private/bin

These folders don't exist and all my keybase folders are owned by root anyway. is this correct?

dschneider@macbookpro227 ~ % ls -l /Volumes/Keybase/
total 0
lr-xr-xr-x  1 root  wheel  0 Sep  8 16:38 private -> /Volumes/Keybase (dschneider)/private
lr-xr-xr-x  1 root  wheel  0 Sep  8 16:38 public -> /Volumes/Keybase (dschneider)/public
lr-xr-xr-x  1 root  wheel  0 Sep  8 16:38 team -> /Volumes/Keybase (dschneider)/team
dschneider@macbookpro227 ~ % ls -l /Volumes/Keybase/private
lr-xr-xr-x  1 root  wheel  0 Sep  8 16:38 /Volumes/Keybase/private -> /Volumes/Keybase (dschneider)/private

I'm also seeing behavior in issue #13390 but I don't see ./bin in my PATH. Also, after I ignore this folder in the gui it immediately reappears in the filesystem.

dschneider@macbookpro227 ~ % echo $PATH
/usr/local/Caskroom/miniconda/base/bin:/usr/local/Caskroom/miniconda/base/condabin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

I'm on macos 11.5.2 with zsh shell. my log id: 234d967e16bfd6bff1e8af1c

any advice?

[maresb]

Potentially related problem here: I'm running on Linux, and some unknown process keeps trying to access /keybase/public/bin. I get a corresponding notification from Keybase that I accessed the public folder for the user named "bin". :joy:

I found this issue by Googling /keybase/private/bin, which I think also is accessed on occasion.

[maresb]

I'm also seeing a notification for /keybase/private/scripts, so I think it is the same issue.

[theangryangel]

On the off chance it helps, I’ve run into this exclusively whilst running VsCode live share. I assume that Code (or an extension) is doing something weird but I’ve not spent any time investigating further as it’s not my usual editor of choice.

[maresb]

Thank you very much @theangryangel, I was indeed just using Live Share!!!

That is really, really bizarre, and also rather concerning.

[andres-lowrie]

I'm not using live-share and I'm also seeing this behavior (I ignore public bin and it keeps re-appearing), the notification that I'm seeing says I've "accessed a public folder" running macos Sonoma 14.0