wireshark-users September 2010 archive
Main Archive Page > Month Archives  > wireshark-users archives
wireshark-users: Re: [Wireshark-users] dumpcap permissions on fi

Re: [Wireshark-users] dumpcap permissions on files created

From: kevin creason <ckevinj_at_nospam>
Date: Fri Sep 03 2010 - 00:29:30 GMT
To: Community support list for Wireshark <wireshark-users@wireshark.org>

I avoid SVN. It's a personal issue...

Would this one below include the group permission change to dumpcap?
http://www.wireshark.org/download/automated/src/wireshark-1.5.0-SVN-34043.tar.bz2

-Kevin
/* I am looking for a lot of men who have an infinite capacity to not know
what can't be done. -- Henry Ford */

On Sat, Aug 28, 2010 at 6:39 AM, Jaap Keuter <jaap.keuter@xs4all.nl> wrote:

> On Sat, 28 Aug 2010 13:09:57 +0200, Sake Blok <sake@euronet.nl> wrote:
> > On 28 aug 2010, at 04:30, kevin creason wrote:
> >
> >> My problem is that files are saved as the user (root, wireshark, or me)
> and 600 permissions no matter what I do with umask, setgid, and setcap. I
> have not found the solution.
> >> I really would like to be able to have group permission so that the team
> can access them without requring dangerous root privilege.
> >>
> >> What's the magic bullet to accomplish this?
> >
> > The file permissions are hardcoded in the source code. I have added
> > the option '-g' to dumpcap to enable group read access as this can
> > indeed be handy when (automatically) capturing to a ringbuffer.
> >
> > To be able to use this feature, you will have to use an automated
> > build[1] with a number higher than 33978 (available in a couple of
> > hours) or wait for the next 1.5.x development release.
> >
> > Cheers,
> >
> >
> > Sake
> >
> > [1] http://www.wireshark.org/download/automated/
>
> I think you need to specify /trunk as well, since trunk-1.0, trunk-1.2
> and trunk-1.4 share the revision number space.
>
> Thanks,
> Jaap
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@wireshark.org
> ?subject=unsubscribe
>

___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@wireshark.org?subject=unsubscribe