Why am I able to open Wireshark in macOS without root privileges?How do I open a file as root in TextEdit on...
A Missing Symbol for This Logo
Is there a Linux system call to create a “view” of a range of a file?
Why am I able to open Wireshark in macOS without root privileges?
Can you tell from a blurry photo if focus was too close or too far?
"on its way" vs. "in its way"
Absorbing damage with Planeswalker
Is using an 'empty' metaphor considered bad style?
How to use Mathematica to do a complex integrate with poles in real axis?
Early credit roll before the end of the film
Which communication protocol is used in AdLib sound card?
Graph with overlapping labels
Consequences of lack of rigour
Has any human ever had the choice to leave Earth permanently?
Is a new Boolean field better than a null reference when a value can be meaningfully absent?
Is it possible to grant users sftp access without shell access? If yes, how is it implemented?
Eww, those bytes are gross
How do you funnel food off a cutting board?
Increment each digit in a number to form a new number
Move fast ...... Or you will lose
Cat is tipping over bed-side lamps during the night
Constexpr if with a non-bool condition
What is the most fuel efficient way out of the Solar System?
Play Zip, Zap, Zop
Dilemma of explaining to interviewer that he is the reason for declining second interview
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?
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
edited 25 mins ago
Cody Gray
2081311
asked 8 hours ago
scipsychoscipsycho
1028
add a comment |
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
edited 25 mins ago
Cody Gray
2081311
asked 8 hours ago
scipsychoscipsycho
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
add a comment |
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
edited 25 mins ago
Cody Gray
2081311
asked 8 hours ago
scipsychoscipsycho
1028
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
root wireshark
edited 25 mins ago
Cody Gray
2081311
asked 8 hours ago
scipsychoscipsycho
1028
edited 25 mins ago
Cody Gray
2081311
asked 8 hours ago
scipsychoscipsycho
1028
edited 25 mins ago
Cody Gray
2081311
edited 25 mins ago
Cody Gray
2081311
edited 25 mins ago
Cody Gray
2081311
2081311
asked 8 hours ago
scipsychoscipsycho
1028
asked 8 hours ago
scipsychoscipsycho
1028
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
add a comment |
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
add a comment |
1 Answer
1
active
oldest
votes
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.
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
add a comment |
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
});
}
});
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%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
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.
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
add a comment |
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.
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
add a comment |
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.
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
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.
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
answered 7 hours ago
jksoegaardjksoegaard
17.8k1747
17.8k1747
add a comment |
add a comment |
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.
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%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
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 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