allow just running of two specific programs (scripts) for user's account
I don't have much experience with user privileges in Raspbian (Debian for Raspberry Pi). Sorry for "stupid" question but I would like to ask you for help with this. (I think it has something to do with privileges.)
My RPi is set to boot to default desktop environment (for default user "pi"). In LXDE I set auto run of my python script after start. Now, I would like to set for this user his account that way, so he will just have privilege for running my python script in /home/pi (or more my scripts I define). All other system functions should be "disabled" for user (I mean he should not be able to run other applications in Raspian or gain sudo access, or change system settings), so I want to prevent another program running via user click. (I hid all desktop icons and taskbar, too)
debian raspberry-pi raspbian
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
asked Mar 24 '16 at 7:44
peter
2571514
add a comment |
I don't have much experience with user privileges in Raspbian (Debian for Raspberry Pi). Sorry for "stupid" question but I would like to ask you for help with this. (I think it has something to do with privileges.)
My RPi is set to boot to default desktop environment (for default user "pi"). In LXDE I set auto run of my python script after start. Now, I would like to set for this user his account that way, so he will just have privilege for running my python script in /home/pi (or more my scripts I define). All other system functions should be "disabled" for user (I mean he should not be able to run other applications in Raspian or gain sudo access, or change system settings), so I want to prevent another program running via user click. (I hid all desktop icons and taskbar, too)
debian raspberry-pi raspbian
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
asked Mar 24 '16 at 7:44
peter
2571514
What will this be used for? What you're asking for isn't really possible, but your underlying goal could perhaps be met some other way. For a normal user,sudoisn't possible by default, so neither is changing the system settings, and you could perhaps give the user a home directory on a filesystem that's mounted noexec to prevent him from executing a file he wrote to, but stopping him from running anything in /usr/bin would require redoing all the permissions (they're alla+x) and then changing everything that depended on the previous permissions. [1/2]
– marinus
Mar 24 '16 at 12:57
However, given that your user doesn't know of any exploits, just not givingsudoaccess should be enough to prevent him from screwing the system up. And if you're trying to have a kiosk-like setup, there are programs available for that. [2/2]
– marinus
Mar 24 '16 at 12:58
thanks, I googled what is "kiosk-like" and yes, it looks it should be something like kiosk.
– peter
Mar 24 '16 at 13:30
add a comment |
I don't have much experience with user privileges in Raspbian (Debian for Raspberry Pi). Sorry for "stupid" question but I would like to ask you for help with this. (I think it has something to do with privileges.)
My RPi is set to boot to default desktop environment (for default user "pi"). In LXDE I set auto run of my python script after start. Now, I would like to set for this user his account that way, so he will just have privilege for running my python script in /home/pi (or more my scripts I define). All other system functions should be "disabled" for user (I mean he should not be able to run other applications in Raspian or gain sudo access, or change system settings), so I want to prevent another program running via user click. (I hid all desktop icons and taskbar, too)
debian raspberry-pi raspbian
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
asked Mar 24 '16 at 7:44
peter
2571514
I don't have much experience with user privileges in Raspbian (Debian for Raspberry Pi). Sorry for "stupid" question but I would like to ask you for help with this. (I think it has something to do with privileges.)
My RPi is set to boot to default desktop environment (for default user "pi"). In LXDE I set auto run of my python script after start. Now, I would like to set for this user his account that way, so he will just have privilege for running my python script in /home/pi (or more my scripts I define). All other system functions should be "disabled" for user (I mean he should not be able to run other applications in Raspian or gain sudo access, or change system settings), so I want to prevent another program running via user click. (I hid all desktop icons and taskbar, too)
debian raspberry-pi raspbian
debian raspberry-pi raspbian
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
asked Mar 24 '16 at 7:44
peter
2571514
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
asked Mar 24 '16 at 7:44
peter
2571514
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
edited Dec 16 at 4:19
Rui F Ribeiro
38.9k1479129
38.9k1479129
asked Mar 24 '16 at 7:44
peter
2571514
asked Mar 24 '16 at 7:44
peter
2571514
asked Mar 24 '16 at 7:44
peter
2571514
2571514
What will this be used for? What you're asking for isn't really possible, but your underlying goal could perhaps be met some other way. For a normal user,sudoisn't possible by default, so neither is changing the system settings, and you could perhaps give the user a home directory on a filesystem that's mounted noexec to prevent him from executing a file he wrote to, but stopping him from running anything in /usr/bin would require redoing all the permissions (they're alla+x) and then changing everything that depended on the previous permissions. [1/2]
– marinus
Mar 24 '16 at 12:57
However, given that your user doesn't know of any exploits, just not givingsudoaccess should be enough to prevent him from screwing the system up. And if you're trying to have a kiosk-like setup, there are programs available for that. [2/2]
– marinus
Mar 24 '16 at 12:58
thanks, I googled what is "kiosk-like" and yes, it looks it should be something like kiosk.
– peter
Mar 24 '16 at 13:30
add a comment |
What will this be used for? What you're asking for isn't really possible, but your underlying goal could perhaps be met some other way. For a normal user,sudoisn't possible by default, so neither is changing the system settings, and you could perhaps give the user a home directory on a filesystem that's mounted noexec to prevent him from executing a file he wrote to, but stopping him from running anything in /usr/bin would require redoing all the permissions (they're alla+x) and then changing everything that depended on the previous permissions. [1/2]
– marinus
Mar 24 '16 at 12:57
However, given that your user doesn't know of any exploits, just not givingsudoaccess should be enough to prevent him from screwing the system up. And if you're trying to have a kiosk-like setup, there are programs available for that. [2/2]
– marinus
Mar 24 '16 at 12:58
thanks, I googled what is "kiosk-like" and yes, it looks it should be something like kiosk.
– peter
Mar 24 '16 at 13:30
What will this be used for? What you're asking for isn't really possible, but your underlying goal could perhaps be met some other way. For a normal user,
sudo isn't possible by default, so neither is changing the system settings, and you could perhaps give the user a home directory on a filesystem that's mounted noexec to prevent him from executing a file he wrote to, but stopping him from running anything in /usr/bin would require redoing all the permissions (they're all a+x) and then changing everything that depended on the previous permissions. [1/2]– marinus
Mar 24 '16 at 12:57
What will this be used for? What you're asking for isn't really possible, but your underlying goal could perhaps be met some other way. For a normal user,
sudo isn't possible by default, so neither is changing the system settings, and you could perhaps give the user a home directory on a filesystem that's mounted noexec to prevent him from executing a file he wrote to, but stopping him from running anything in /usr/bin would require redoing all the permissions (they're all a+x) and then changing everything that depended on the previous permissions. [1/2]– marinus
Mar 24 '16 at 12:57
However, given that your user doesn't know of any exploits, just not giving
sudo access should be enough to prevent him from screwing the system up. And if you're trying to have a kiosk-like setup, there are programs available for that. [2/2]– marinus
Mar 24 '16 at 12:58
However, given that your user doesn't know of any exploits, just not giving
sudo access should be enough to prevent him from screwing the system up. And if you're trying to have a kiosk-like setup, there are programs available for that. [2/2]– marinus
Mar 24 '16 at 12:58
thanks, I googled what is "kiosk-like" and yes, it looks it should be something like kiosk.
– peter
Mar 24 '16 at 13:30
thanks, I googled what is "kiosk-like" and yes, it looks it should be something like kiosk.
– peter
Mar 24 '16 at 13:30
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f271884%2fallow-just-running-of-two-specific-programs-scripts-for-users-account%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f271884%2fallow-just-running-of-two-specific-programs-scripts-for-users-account%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What will this be used for? What you're asking for isn't really possible, but your underlying goal could perhaps be met some other way. For a normal user,
sudoisn't possible by default, so neither is changing the system settings, and you could perhaps give the user a home directory on a filesystem that's mounted noexec to prevent him from executing a file he wrote to, but stopping him from running anything in /usr/bin would require redoing all the permissions (they're alla+x) and then changing everything that depended on the previous permissions. [1/2]– marinus
Mar 24 '16 at 12:57
However, given that your user doesn't know of any exploits, just not giving
sudoaccess should be enough to prevent him from screwing the system up. And if you're trying to have a kiosk-like setup, there are programs available for that. [2/2]– marinus
Mar 24 '16 at 12:58
thanks, I googled what is "kiosk-like" and yes, it looks it should be something like kiosk.
– peter
Mar 24 '16 at 13:30