Are these commands materially, or only semantically different?
In a shell script that's using curl to fetch a script, then executing it, are these two approaches materially different?
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
...vs...
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
There's something about the sudo right before curl in the second command that's giving me pause, but I can't articulate whether or how it's different (riskier?) than the first.
shell-script curl
asked Jan 22 at 17:55
rotarydialrotarydial
1086
add a comment |
In a shell script that's using curl to fetch a script, then executing it, are these two approaches materially different?
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
...vs...
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
There's something about the sudo right before curl in the second command that's giving me pause, but I can't articulate whether or how it's different (riskier?) than the first.
shell-script curl
asked Jan 22 at 17:55
rotarydialrotarydial
1086
1
There is never a reason to runcurlwithsudo.
– Kusalananda
Jan 22 at 18:01
add a comment |
In a shell script that's using curl to fetch a script, then executing it, are these two approaches materially different?
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
...vs...
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
There's something about the sudo right before curl in the second command that's giving me pause, but I can't articulate whether or how it's different (riskier?) than the first.
shell-script curl
asked Jan 22 at 17:55
rotarydialrotarydial
1086
In a shell script that's using curl to fetch a script, then executing it, are these two approaches materially different?
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
...vs...
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
There's something about the sudo right before curl in the second command that's giving me pause, but I can't articulate whether or how it's different (riskier?) than the first.
shell-script curl
shell-script curl
asked Jan 22 at 17:55
rotarydialrotarydial
1086
asked Jan 22 at 17:55
rotarydialrotarydial
1086
asked Jan 22 at 17:55
rotarydialrotarydial
1086
asked Jan 22 at 17:55
rotarydialrotarydial
1086
asked Jan 22 at 17:55
rotarydialrotarydial
1086
1086
1
There is never a reason to runcurlwithsudo.
– Kusalananda
Jan 22 at 18:01
add a comment |
1
There is never a reason to runcurlwithsudo.
– Kusalananda
Jan 22 at 18:01
1
1
There is never a reason to run
curl with sudo.– Kusalananda
Jan 22 at 18:01
There is never a reason to run
curl with sudo.– Kusalananda
Jan 22 at 18:01
add a comment |
1 Answer
1
active
oldest
votes
There are a number of material differences.
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
runs curl as the current user, and tee as root; it also clears the contents of /usr/bin/dosomething.sh before writing to it.
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
runs curl as root, and tries to append to /usr/bin/dosomething.sh with the permissions of the current user (the current shell sets the redirection up).
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
add a comment |
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%2f496020%2fare-these-commands-materially-or-only-semantically-different%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are a number of material differences.
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
runs curl as the current user, and tee as root; it also clears the contents of /usr/bin/dosomething.sh before writing to it.
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
runs curl as root, and tries to append to /usr/bin/dosomething.sh with the permissions of the current user (the current shell sets the redirection up).
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
add a comment |
There are a number of material differences.
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
runs curl as the current user, and tee as root; it also clears the contents of /usr/bin/dosomething.sh before writing to it.
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
runs curl as root, and tries to append to /usr/bin/dosomething.sh with the permissions of the current user (the current shell sets the redirection up).
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
add a comment |
There are a number of material differences.
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
runs curl as the current user, and tee as root; it also clears the contents of /usr/bin/dosomething.sh before writing to it.
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
runs curl as root, and tries to append to /usr/bin/dosomething.sh with the permissions of the current user (the current shell sets the redirection up).
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
There are a number of material differences.
curl http://address-to-some-script/dosomething.sh | sudo tee /usr/bin/dosomething.sh
runs curl as the current user, and tee as root; it also clears the contents of /usr/bin/dosomething.sh before writing to it.
sudo curl http://address-to-some-script/dosomething.sh >> /usr/bin/dosomething.sh
runs curl as root, and tries to append to /usr/bin/dosomething.sh with the permissions of the current user (the current shell sets the redirection up).
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
answered Jan 22 at 17:59
Stephen KittStephen Kitt
169k24380458
169k24380458
add a comment |
add a comment |
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%2f496020%2fare-these-commands-materially-or-only-semantically-different%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
1
There is never a reason to run
curlwithsudo.– Kusalananda
Jan 22 at 18:01