Are these commands materially, or only semantically different?












1















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.










share|improve this question


















  • 1





    There is never a reason to run curl with sudo.

    – Kusalananda
    12 hours ago
















1















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.










share|improve this question


















  • 1





    There is never a reason to run curl with sudo.

    – Kusalananda
    12 hours ago














1












1








1








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.










share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 12 hours ago









rotarydialrotarydial

1066




1066








  • 1





    There is never a reason to run curl with sudo.

    – Kusalananda
    12 hours ago














  • 1





    There is never a reason to run curl with sudo.

    – Kusalananda
    12 hours ago








1




1





There is never a reason to run curl with sudo.

– Kusalananda
12 hours ago





There is never a reason to run curl with sudo.

– Kusalananda
12 hours ago










1 Answer
1






active

oldest

votes


















6














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).






share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    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









    6














    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).






    share|improve this answer




























      6














      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).






      share|improve this answer


























        6












        6








        6







        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).






        share|improve this answer













        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).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 12 hours ago









        Stephen KittStephen Kitt

        168k24378456




        168k24378456






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?