Question regarding sudo & crontab
I just created a script that is being run as a @reboot item in crontab -e.
It runs two scripts...in order. One creates ramdisks and populates them, and another runs an executable that depends on those ramdisks.
The first script looks like this:
#! /bin/bash
cd ~/trlserver/nginx
mkdir -p logs
sudo mount -t tmpfs -o size=1024M tmpfs logs
sudo chown $(whoami): logs
cd ~/trlserver/data
mkdir -p 20180927_na2018_ramdisk
sudo mount -t tmpfs -o size=5G tmpfs 20180927_na2018_ramdisk
sudo chown $(whoami): 20180927_na2018_ramdisk
cp -a 20180927_na2018/* 20180927_na2018_ramdisk
cp -a 20180927_na2018.additions/* 20180927_na2018_ramdisk
I've read the accepted answer here:
https://askubuntu.com/questions/173924/how-to-run-a-cron-job-using-the-sudo-command
Questions:
1) I could move this to be run separately (sudo crontab -e), and hardcode the user name, but how do I guarantee it would be executed before the script that depends on it?
2) What prevents an attacker from creating a cron job (crontab -e) that uses sudo set to run one minute from the current time...effectively bypassing password entry for use of sudo? (I tried this and it seemed to work)
sudo cron
add a comment |
I just created a script that is being run as a @reboot item in crontab -e.
It runs two scripts...in order. One creates ramdisks and populates them, and another runs an executable that depends on those ramdisks.
The first script looks like this:
#! /bin/bash
cd ~/trlserver/nginx
mkdir -p logs
sudo mount -t tmpfs -o size=1024M tmpfs logs
sudo chown $(whoami): logs
cd ~/trlserver/data
mkdir -p 20180927_na2018_ramdisk
sudo mount -t tmpfs -o size=5G tmpfs 20180927_na2018_ramdisk
sudo chown $(whoami): 20180927_na2018_ramdisk
cp -a 20180927_na2018/* 20180927_na2018_ramdisk
cp -a 20180927_na2018.additions/* 20180927_na2018_ramdisk
I've read the accepted answer here:
https://askubuntu.com/questions/173924/how-to-run-a-cron-job-using-the-sudo-command
Questions:
1) I could move this to be run separately (sudo crontab -e), and hardcode the user name, but how do I guarantee it would be executed before the script that depends on it?
2) What prevents an attacker from creating a cron job (crontab -e) that uses sudo set to run one minute from the current time...effectively bypassing password entry for use of sudo? (I tried this and it seemed to work)
sudo cron
add a comment |
I just created a script that is being run as a @reboot item in crontab -e.
It runs two scripts...in order. One creates ramdisks and populates them, and another runs an executable that depends on those ramdisks.
The first script looks like this:
#! /bin/bash
cd ~/trlserver/nginx
mkdir -p logs
sudo mount -t tmpfs -o size=1024M tmpfs logs
sudo chown $(whoami): logs
cd ~/trlserver/data
mkdir -p 20180927_na2018_ramdisk
sudo mount -t tmpfs -o size=5G tmpfs 20180927_na2018_ramdisk
sudo chown $(whoami): 20180927_na2018_ramdisk
cp -a 20180927_na2018/* 20180927_na2018_ramdisk
cp -a 20180927_na2018.additions/* 20180927_na2018_ramdisk
I've read the accepted answer here:
https://askubuntu.com/questions/173924/how-to-run-a-cron-job-using-the-sudo-command
Questions:
1) I could move this to be run separately (sudo crontab -e), and hardcode the user name, but how do I guarantee it would be executed before the script that depends on it?
2) What prevents an attacker from creating a cron job (crontab -e) that uses sudo set to run one minute from the current time...effectively bypassing password entry for use of sudo? (I tried this and it seemed to work)
sudo cron
I just created a script that is being run as a @reboot item in crontab -e.
It runs two scripts...in order. One creates ramdisks and populates them, and another runs an executable that depends on those ramdisks.
The first script looks like this:
#! /bin/bash
cd ~/trlserver/nginx
mkdir -p logs
sudo mount -t tmpfs -o size=1024M tmpfs logs
sudo chown $(whoami): logs
cd ~/trlserver/data
mkdir -p 20180927_na2018_ramdisk
sudo mount -t tmpfs -o size=5G tmpfs 20180927_na2018_ramdisk
sudo chown $(whoami): 20180927_na2018_ramdisk
cp -a 20180927_na2018/* 20180927_na2018_ramdisk
cp -a 20180927_na2018.additions/* 20180927_na2018_ramdisk
I've read the accepted answer here:
https://askubuntu.com/questions/173924/how-to-run-a-cron-job-using-the-sudo-command
Questions:
1) I could move this to be run separately (sudo crontab -e), and hardcode the user name, but how do I guarantee it would be executed before the script that depends on it?
2) What prevents an attacker from creating a cron job (crontab -e) that uses sudo set to run one minute from the current time...effectively bypassing password entry for use of sudo? (I tried this and it seemed to work)
sudo cron
sudo cron
asked 2 hours ago
zzxyzzzxyz
16410
16410
add a comment |
add a comment |
0
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%2f505740%2fquestion-regarding-sudo-crontab%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
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.
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%2f505740%2fquestion-regarding-sudo-crontab%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