Is there a way to limit write access to a filesystem based on the executable?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I would like to reasonably ensure that only a specific executable has write access to a filesystem (anything else is just read access).



I do not need this to be secure (in the sense this is not a security feature to protect access by malicious entities), this is rather a safety net for some data (which are brought in by a single executable and otherwise open for read).



Does such a mechanism exist?







share|improve this question



















  • I am not sure about what you are asking but how about: Mount the filesystem with a specific user that has write access and read access for group and other. Set the executable to that user.
    – Rinzwind
    Jun 1 at 7:39














up vote
0
down vote

favorite












I would like to reasonably ensure that only a specific executable has write access to a filesystem (anything else is just read access).



I do not need this to be secure (in the sense this is not a security feature to protect access by malicious entities), this is rather a safety net for some data (which are brought in by a single executable and otherwise open for read).



Does such a mechanism exist?







share|improve this question



















  • I am not sure about what you are asking but how about: Mount the filesystem with a specific user that has write access and read access for group and other. Set the executable to that user.
    – Rinzwind
    Jun 1 at 7:39












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I would like to reasonably ensure that only a specific executable has write access to a filesystem (anything else is just read access).



I do not need this to be secure (in the sense this is not a security feature to protect access by malicious entities), this is rather a safety net for some data (which are brought in by a single executable and otherwise open for read).



Does such a mechanism exist?







share|improve this question











I would like to reasonably ensure that only a specific executable has write access to a filesystem (anything else is just read access).



I do not need this to be secure (in the sense this is not a security feature to protect access by malicious entities), this is rather a safety net for some data (which are brought in by a single executable and otherwise open for read).



Does such a mechanism exist?









share|improve this question










share|improve this question




share|improve this question









asked Jun 1 at 7:30









WoJ

4232924




4232924











  • I am not sure about what you are asking but how about: Mount the filesystem with a specific user that has write access and read access for group and other. Set the executable to that user.
    – Rinzwind
    Jun 1 at 7:39
















  • I am not sure about what you are asking but how about: Mount the filesystem with a specific user that has write access and read access for group and other. Set the executable to that user.
    – Rinzwind
    Jun 1 at 7:39















I am not sure about what you are asking but how about: Mount the filesystem with a specific user that has write access and read access for group and other. Set the executable to that user.
– Rinzwind
Jun 1 at 7:39




I am not sure about what you are asking but how about: Mount the filesystem with a specific user that has write access and read access for group and other. Set the executable to that user.
– Rinzwind
Jun 1 at 7:39















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1042533%2fis-there-a-way-to-limit-write-access-to-a-filesystem-based-on-the-executable%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1042533%2fis-there-a-way-to-limit-write-access-to-a-filesystem-based-on-the-executable%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491