As stated in the release notes of macOS 10.15 beta 7 and 8 the behavior of access(2) has been restored to that of macOS Mojave. (47309955) Therefore, access always returns true for filesystem locations that are privacy-protected. Since this the recommended way to check for privacy-protected filesystem locations - as stated in “Advances in macOS security” - i would like to know if the behavior of the call will be correct (like in beta 6) in the next or final version of macOS 10.15?
The problem behind my question is that our filetransfer solution makes use of this call in order to prevent our app from being blocked (prompt for access on the remote side that can't be granted since no one is sitting in fron of the machine), if the a client tries to navigate into a privacy-protected filesystem location on a remote machine running macOS 10.15 within the scope of a headless filetransfer session. Or are there other solutions in order to tackle this problem?
