Re: [Wireshark-users] Wireshark sudo
If the machine has /dev/bpf* you should chmod these to be readable and writable by the users instead of suexecing wireshark. On 4/3/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am setting up a laptop to be used as (and only as) a network analysis machine. Wireshark is set up to be run sudo root. The problem is that any capture files saved by Wireshark are owned by root with permission 600. After the non-root user runs wireshark (sudo), he needs to be able to copy or move the files. I've tried changing the umask under which the script to launch wireshark runs, but that gets ignored. So maybe it is Wireshark itself (rather then the shell) setting the permissions of saved files? ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Wireshark sudo
On Tue, Apr 03, 2007 at 02:35:49PM +, [EMAIL PROTECTED] wrote: I've tried changing the umask under which the script to launch wireshark runs, but that gets ignored. So maybe it is Wireshark itself (rather then the shell) setting the permissions of saved files? Yes, Wireshark sets the umask on the temporary file it uses while capturing (look for the umask() call in tempfile.c). For saved files, I believe the temporary file is simply copied over with the same permissions it was created with. Steve ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
