Why am I able to open Wireshark in macOS without root privileges?How do I open a file as root in TextEdit on...

Why am I able to open Wireshark in macOS without root privileges?

How do you catch Smeargle in Pokemon Go?

Why exactly do action photographers need high fps burst cameras?

Absorbing damage with Planeswalker

Why is it that Bernie Sanders is always called a "socialist"?

Graph with overlapping labels

It took me a lot of time to make this, pls like. (YouTube Comments #1)

In mixed effect models, how account for grouped random effects?

Can we harness gravitational potential energy?

What does it mean for a caliber to be flat shooting?

Why is working on the same position for more than 15 years not a red flag?

Why TEventArgs wasn't made contravariant in standard event pattern in the .Net ecosystem?

Do authors have to be politically correct in article-writing?

What is the proper way to reproach a rav?

Can my spouse sponsor me for a UK visa if I am unemployed?

Why are the books in the Game of Thrones citadel library shelved spine inwards?

Is using an 'empty' metaphor considered bad style?

False written accusations not made public - is there law to cover this?

Finding a logistic regression model which can achieve zero error on a training set training data for a binary classification problem with two features

Why zero tolerance on nudity in space?

How do I draw the dashed lines as shown in this figure

Is there a Linux system call to create a “view” of a range of a file?

Eww, those bytes are gross

Does every functor from Set to Set preserve products?



Why am I able to open Wireshark in macOS without root privileges?


How do I open a file as root in TextEdit on Lion?How do I execute a bash script that requires root privileges?How to open the finder as rootWhy Doesn't OSX root user automatically default to the same shell as other usersiPhone 5S broken screen root access without iTunes authorizationNot able to write a file with rootHow do I protect myself from the root vulnerability in macOS High Sierra?Difference between macOS login root and Darwin Terminal rootHow do I ensure that the macOS root account bug is fully fixed on my machine?Easiest way to definitely, positively delete a file in macOS (10.14+) as root?













5















As far as I know, capturing packets using Wireshark requires root/administrator privileges. In Windows, it prompts for UAC elevation and runs with administrative privileges. The same thing in Ubuntu; it prompts for a password to authorize access before showing me the interfaces.



However, in macOS, there is no authorization required. I don't have to enter a password. Instead, Wireshark is directly showing me the interfaces and I am able to capture packets.



How is Wireshark able to do this on macOS? What is special about macOS that allows interfaces and packets to be monitored without administrative access?










share|improve this question

























  • What kind of wireshark are you running? GUI (app) or command line?

    – IconDaemon
    7 hours ago











  • Did you login as a standard user or as an administrator user?

    – jksoegaard
    7 hours ago
















5















As far as I know, capturing packets using Wireshark requires root/administrator privileges. In Windows, it prompts for UAC elevation and runs with administrative privileges. The same thing in Ubuntu; it prompts for a password to authorize access before showing me the interfaces.



However, in macOS, there is no authorization required. I don't have to enter a password. Instead, Wireshark is directly showing me the interfaces and I am able to capture packets.



How is Wireshark able to do this on macOS? What is special about macOS that allows interfaces and packets to be monitored without administrative access?










share|improve this question

























  • What kind of wireshark are you running? GUI (app) or command line?

    – IconDaemon
    7 hours ago











  • Did you login as a standard user or as an administrator user?

    – jksoegaard
    7 hours ago














5












5








5








As far as I know, capturing packets using Wireshark requires root/administrator privileges. In Windows, it prompts for UAC elevation and runs with administrative privileges. The same thing in Ubuntu; it prompts for a password to authorize access before showing me the interfaces.



However, in macOS, there is no authorization required. I don't have to enter a password. Instead, Wireshark is directly showing me the interfaces and I am able to capture packets.



How is Wireshark able to do this on macOS? What is special about macOS that allows interfaces and packets to be monitored without administrative access?










share|improve this question
















As far as I know, capturing packets using Wireshark requires root/administrator privileges. In Windows, it prompts for UAC elevation and runs with administrative privileges. The same thing in Ubuntu; it prompts for a password to authorize access before showing me the interfaces.



However, in macOS, there is no authorization required. I don't have to enter a password. Instead, Wireshark is directly showing me the interfaces and I am able to capture packets.



How is Wireshark able to do this on macOS? What is special about macOS that allows interfaces and packets to be monitored without administrative access?







root wireshark






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 30 mins ago









Cody Gray

2081311




2081311










asked 8 hours ago









scipsychoscipsycho

1028




1028













  • What kind of wireshark are you running? GUI (app) or command line?

    – IconDaemon
    7 hours ago











  • Did you login as a standard user or as an administrator user?

    – jksoegaard
    7 hours ago



















  • What kind of wireshark are you running? GUI (app) or command line?

    – IconDaemon
    7 hours ago











  • Did you login as a standard user or as an administrator user?

    – jksoegaard
    7 hours ago

















What kind of wireshark are you running? GUI (app) or command line?

– IconDaemon
7 hours ago





What kind of wireshark are you running? GUI (app) or command line?

– IconDaemon
7 hours ago













Did you login as a standard user or as an administrator user?

– jksoegaard
7 hours ago





Did you login as a standard user or as an administrator user?

– jksoegaard
7 hours ago










1 Answer
1






active

oldest

votes


















9














The reason is that the Wireshark installer installs a LaunchDaemon (i.e. something that runs with superuser privileges on boot) for setting special permissions to capture network packets. More specifically you can look at the file /Library/LaunchDaemon/org.wireshark.ChmodBPF.plist to see what it does and when it is run.



As creating these LaunchDaemons require superuser privileges in itself, the Wireshark installer requires you to be a superuser (i.e. you have to enter an administrator user password to install the software).



If you look at the actual script run by the LaunchDaemon in /Library/Application Support/Wireshark/ChmodBPF/ChmodBPF, you'll see that it creates 256 devices entries /dev/bpf0 to /dev/bpf255 and sets to that everyone in the access_bpf group can read and write to these device files.



The access_bpf groups is actually also created by Wireshark installer. This also requires superuser privileges. If you open System Preferences and then Users & Groups, you'll be able to fold out the "Groups" part of the tree and see "access_bpf" listed there. You can then add/remove users from that group to give or remove permission to capture network packets within Wireshark.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "118"
    };
    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%2fapple.stackexchange.com%2fquestions%2f352593%2fwhy-am-i-able-to-open-wireshark-in-macos-without-root-privileges%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









    9














    The reason is that the Wireshark installer installs a LaunchDaemon (i.e. something that runs with superuser privileges on boot) for setting special permissions to capture network packets. More specifically you can look at the file /Library/LaunchDaemon/org.wireshark.ChmodBPF.plist to see what it does and when it is run.



    As creating these LaunchDaemons require superuser privileges in itself, the Wireshark installer requires you to be a superuser (i.e. you have to enter an administrator user password to install the software).



    If you look at the actual script run by the LaunchDaemon in /Library/Application Support/Wireshark/ChmodBPF/ChmodBPF, you'll see that it creates 256 devices entries /dev/bpf0 to /dev/bpf255 and sets to that everyone in the access_bpf group can read and write to these device files.



    The access_bpf groups is actually also created by Wireshark installer. This also requires superuser privileges. If you open System Preferences and then Users & Groups, you'll be able to fold out the "Groups" part of the tree and see "access_bpf" listed there. You can then add/remove users from that group to give or remove permission to capture network packets within Wireshark.






    share|improve this answer




























      9














      The reason is that the Wireshark installer installs a LaunchDaemon (i.e. something that runs with superuser privileges on boot) for setting special permissions to capture network packets. More specifically you can look at the file /Library/LaunchDaemon/org.wireshark.ChmodBPF.plist to see what it does and when it is run.



      As creating these LaunchDaemons require superuser privileges in itself, the Wireshark installer requires you to be a superuser (i.e. you have to enter an administrator user password to install the software).



      If you look at the actual script run by the LaunchDaemon in /Library/Application Support/Wireshark/ChmodBPF/ChmodBPF, you'll see that it creates 256 devices entries /dev/bpf0 to /dev/bpf255 and sets to that everyone in the access_bpf group can read and write to these device files.



      The access_bpf groups is actually also created by Wireshark installer. This also requires superuser privileges. If you open System Preferences and then Users & Groups, you'll be able to fold out the "Groups" part of the tree and see "access_bpf" listed there. You can then add/remove users from that group to give or remove permission to capture network packets within Wireshark.






      share|improve this answer


























        9












        9








        9







        The reason is that the Wireshark installer installs a LaunchDaemon (i.e. something that runs with superuser privileges on boot) for setting special permissions to capture network packets. More specifically you can look at the file /Library/LaunchDaemon/org.wireshark.ChmodBPF.plist to see what it does and when it is run.



        As creating these LaunchDaemons require superuser privileges in itself, the Wireshark installer requires you to be a superuser (i.e. you have to enter an administrator user password to install the software).



        If you look at the actual script run by the LaunchDaemon in /Library/Application Support/Wireshark/ChmodBPF/ChmodBPF, you'll see that it creates 256 devices entries /dev/bpf0 to /dev/bpf255 and sets to that everyone in the access_bpf group can read and write to these device files.



        The access_bpf groups is actually also created by Wireshark installer. This also requires superuser privileges. If you open System Preferences and then Users & Groups, you'll be able to fold out the "Groups" part of the tree and see "access_bpf" listed there. You can then add/remove users from that group to give or remove permission to capture network packets within Wireshark.






        share|improve this answer













        The reason is that the Wireshark installer installs a LaunchDaemon (i.e. something that runs with superuser privileges on boot) for setting special permissions to capture network packets. More specifically you can look at the file /Library/LaunchDaemon/org.wireshark.ChmodBPF.plist to see what it does and when it is run.



        As creating these LaunchDaemons require superuser privileges in itself, the Wireshark installer requires you to be a superuser (i.e. you have to enter an administrator user password to install the software).



        If you look at the actual script run by the LaunchDaemon in /Library/Application Support/Wireshark/ChmodBPF/ChmodBPF, you'll see that it creates 256 devices entries /dev/bpf0 to /dev/bpf255 and sets to that everyone in the access_bpf group can read and write to these device files.



        The access_bpf groups is actually also created by Wireshark installer. This also requires superuser privileges. If you open System Preferences and then Users & Groups, you'll be able to fold out the "Groups" part of the tree and see "access_bpf" listed there. You can then add/remove users from that group to give or remove permission to capture network packets within Wireshark.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 7 hours ago









        jksoegaardjksoegaard

        17.8k1747




        17.8k1747






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Different!


            • 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%2fapple.stackexchange.com%2fquestions%2f352593%2fwhy-am-i-able-to-open-wireshark-in-macos-without-root-privileges%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

            Benedict Cumberbatch Contingut Inicis Debut professional Premis Filmografia bàsica Premis i...

            Monticle de plataforma Contingut Est de Nord Amèrica Interpretacions Altres cultures Vegeu...

            Escacs Janus Enllaços externs Menú de navegacióEscacs JanusJanusschachBrainKing.comChessV