Fix potential security flaw in creation of sockets/directories #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See commit 8dc2877f8dbdf4161c394c28e714ee3efd645cf5
Well, I fixed last bit I didn't like in su-binary as promised. There is more stuff to fix:
(requires change in corresponding macro only)
Thus, su-binary won't touch flash, /dev is tmpfs nowadays
su-binary acess db only once, so db open/close can be moved to database_check
The socket is created once per su invocation. We can use pid in the socket name.
It's neither "safer" nor "weaker"
If you'll agree to accept mentioned changes I could prepare the patches.