sentry-native database permissions on OSX #1117
Replies: 1 comment 1 reply
-
Even if you change the permissions of the database path after Sentry is initialized, the user executing the process will also own every subsequent file written to that directory.
The folder has these permissions because the process is executed by You have essentially two options:
Again, the latter should be clarified with the peeps requiring elevated security for that process in the first place. However, the database path only has those permissions because a particular user executes the process. The SDK does not change the permissions in any way. |
Beta Was this translation helpful? Give feedback.
-
I work on a project that uses a user-space process communicating with a service running with elevated privileges. For both processes sentry is configured sentry. However, in certain cases, the automatic transport of the crashes to the server is disabled. For that cases there's a shell script that takes crashdumps from database/completed, then zips them to allows user to send us (developers) for analysis.
The problem is that database folder has permissions, that allow only the owner to see the files inside. And for the elevated service, database path owner is a root, hence we cannot copy the dumps with the script run by a regular user.
My question is about my idea to solve the issue. I was thinking that after I launch the sentry, I could change the permissions for database folder allowing anyone to read it. I'm, however, concerned about possible security issues. This folder has that permissions for some reason, and I'm simply worried that changing permissions wouldn't be a security hole.
Is my solution correct, or would someone suggest something else?
Beta Was this translation helpful? Give feedback.
All reactions