Thread

1. moecables · 1790972047 · focus · HN ↗

   IMHO, it's good to add more specific controls for this. After reading this, I went and checked my list of app with full disk access:

   - Ghostty (fine, it's my terminal)

   - Alfred (fine, I use it for searching everywhere)

   Then I have a few turned off:

   - Spotify (why does it need full disk access) ??

   - Gemini (nope, don't need it to know everything about my computer)

   1. 0c3ca83 · 1790986241 · focus · HN ↗

      - Ghostty (fine, it's my terminal)

      But your terminal shouldn't be accessing any files; you just need to be able to launch /bin/zsh or whatever you use as your shell. The shell needs to be able to access files, but its container doesn't.

      Of course, you could go farther. For example, on OpenBSD, even /bin/ksh has been somewhat sandboxed; it can see most of the file system, but the things it can do have been limited:

        if (pledge("stdio rpath wpath cpath fattr flock getpw proc "
            "exec tty id", NULL) == -1) {

      1. rolosa · 1790987383 · focus · HN ↗

         If you try to ls / for example it's going to pop up a request to access your disk, multiple times. It's rather annoying.

         1. 0c3ca83 · 1790993736 · focus · HN ↗

            Why would ghostty try to access your disk when you run 'ls /'? ghostty isn't opening any files -- ls is.

            1. dcrazy · 1790996030 · focus · HN ↗

               The TCC system attributes the access to Ghostty because that’s the thing the user understands as the app they are interacting with. Otherwise every `posix_spawn()` and `system()` call would result in a new TCC prompt attributed to an inscrutable name.

Unofficial Hacker News client; not affiliated with Y Combinator.