Re: [Wireshark-dev] need some more information on bug 8454

Hi Jeff, > >> I am debugging Wireshark using glibtool ( using OS X 10.8 ) . >> >> I tried to print the log using following ways : >> + printf(" my method is called "); >> + g_print("my method is called "); >> + g_warning("my method is called "); >> >> but none of them worked for me. >> > > All of

Re: [Wireshark-dev] GSoC 2013 Project Proposal for Root permissions in wireshark

> Most systems running Wireshark aren't Linux systems. Thanks. As in the ideas page the statement read " a way to capture packets on Linux and OS X" , only linux came to my mind. > BTW, TShark and Wireshark currently communicate with dumpcap using an, > err, umm, pipe > Currenlty in deb

Re: [Wireshark-dev] GSoC 2013 Project Proposal for Root permissions in wireshark

On May 1, 2013, at 8:58 PM, Mohana Sai wrote: > Sorry for not being specific in the previous mail. > > I was thinking about adding ACL to dumpcap file. I.e., set an ACL limiting who is allowed to execute it? Do *ALL* file systems on which dumpcap might reside support ACLs? > And if many syst

Re: [Wireshark-dev] GSoC 2013 Project Proposal for Root permissions in wireshark

Sorry for not being specific in the previous mail. I was thinking about adding ACL to dumpcap file. And if many systems don't have D-Bus by default, we can use some IPC which is very common in linux systems (unix pipes came to mind, but not sure if it is supported in all linux systems and I read

[Wireshark-dev] Process Information [GSoC]

i have submitted my proposal in wireshark.Can you suggest any changes that would be required ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.

Re: [Wireshark-dev] Bluetooth coloring rules

Would it be useful to allow multiple sets of coloring rules, not associated with a profile, and to have profiles support having more than one set of coloring rules associated with them, evaluated in the order in which they're listed? We could then ship a simple "starter" set and include various

Re: [Wireshark-dev] need some more information on bug 8454

On 05/01/13 14:44, Subh. Singh wrote: Hi Jeff, I am debugging Wireshark using glibtool ( using OS X 10.8 ) . I tried to print the log using following ways : + printf(" my method is called "); + g_print("my method is called "); + g_warning("my method is called "); but none of them worked for m

Re: [Wireshark-dev] Bluetooth coloring rules

On May 1, 2013, at 2:15 PM, Gerald Combs wrote: > Traditionally the default colorfilters file contained a minimal set of > rules focused on general troubleshooting. A case could be made to add > rules for WiFi, storage, telephony, and other types of traffic but we > haven't done so mainly becaus

Re: [Wireshark-dev] Bluetooth coloring rules

On 5/1/13 10:28 AM, michal.labed...@tieto.com wrote: > > What exactly "move to Bluetooth specific global configuration profile" means? > Now using Wireshark is flexible: I open Bluetooth logs or eth-logs in another > Wireshark session. Also remember about possibility to see Bluetooth protocols > o

Re: [Wireshark-dev] Filebacked-tvbuffs : GSoC'13

On 05/01/13 12:16, Anders Broman wrote: Ambarisha B skrev 2013-05-01 17:01: On Thu, Apr 25, 2013 at 7:34 PM, Jeff Morriss mailto:jeff.morriss...@gmail.com>> wrote: [...] >What will this data member contain in case of a reassembly implementation which uses file backed tvbuffs? file pointer(s)

Re: [Wireshark-dev] Filebacked-tvbuffs : GSoC'13

On 05/01/13 11:01, Ambarisha B wrote: On Thu, Apr 25, 2013 at 7:34 PM, Jeff Morriss mailto:jeff.morriss...@gmail.com>> wrote: But the dissectors create the tvb from the reassembled data. So, if we define a new type of tvbuff which has to be used, wouldn't that eff

Re: [Wireshark-dev] Wireshark 1.10.0rc1 is now available

On Wed, May 1, 2013 at 3:09 PM, Reinhard Speyerer wrote: > Gerald Combs wrote: > >> I'm proud to announce the release of Wireshark 1.10.0rc1. This is the >> first release candidate for Wireshark 1.10.0. > > Hi Gerald, > > unfortunately Wireshark 1.10.0rc1 no longer builds with glib 2.14 as > wmem

Re: [Wireshark-dev] Wireshark 1.10.0rc1 is now available

Gerald Combs wrote: > I'm proud to announce the release of Wireshark 1.10.0rc1. This is the > first release candidate for Wireshark 1.10.0. Hi Gerald, unfortunately Wireshark 1.10.0rc1 no longer builds with glib 2.14 as wmem_test.c uses several g_test_* functions that were only introduced in gl

Re: [Wireshark-dev] need some more information on bug 8454

Hi Jeff, I am debugging Wireshark using glibtool ( using OS X 10.8 ) . I tried to print the log using following ways : + printf(" my method is called "); + g_print("my method is called "); + g_warning("my method is called "); but none of them worked for me. Sorry for previous blank link. Pleas

Re: [Wireshark-dev] GSoC 2013 Project Proposal for Root permissions in wireshark

On May 1, 2013, at 10:48 AM, Mohana Sai wrote: > I am little confused about this project. What requirements the project > doesn't meet if we use any of these 2 methods > > By simply adding ACL? Adding an ACL to what? > By separating the code in to privileged part and unprivileged part and us

Re: [Wireshark-dev] GSoC 2013 Project Proposal for Root permissions in wireshark

I am little confused about this project. What requirements the project doesn't meet if we use any of these 2 methods By simply adding ACL? By separating the code in to privileged part and unprivileged part and using DBus to communicate the privileged part with unprivileged one ? Regards, MohanaSa

Re: [Wireshark-dev] Bluetooth coloring rules

Hi, > On Tue, Apr 30, 2013 at 7:54 PM, Gerald Combs wrote: >> About half of our coloring rules are for various Bluetooth protocols. >> Would anyone object to moving them to a Bluetooth-specific global >> configuration profile? I don't think they belong in the default profile >> but I'd rather not

[Wireshark-dev] About the compile

Hi, all Now, i want to convert "tshark" to a library(I can use it in my code). Here is the steps what I did: 1 Made a tshark.c copy which was called "tshark_bk.c??; Modified the entrance function "main" to the any other name, such as "tshark_entrance". 2 Added the following statement to the Ma

Re: [Wireshark-dev] Filebacked-tvbuffs : GSoC'13

Ambarisha B skrev 2013-05-01 17:01: On Thu, Apr 25, 2013 at 7:34 PM, Jeff Morriss mailto:jeff.morriss...@gmail.com>> wrote: But the dissectors create the tvb from the reassembled data. So, if we define a new type of tvbuff which has to be used, wouldn't that effe

Re: [Wireshark-dev] Filebacked-tvbuffs : GSoC'13

On Thu, Apr 25, 2013 at 7:34 PM, Jeff Morriss wrote: > But the dissectors create the tvb from the reassembled data. So, if we >> define a new type of tvbuff which has to be used, wouldn't that effect >> the dissectors? >> > > It shouldn't: dissectors should be using the TVB-accessor functions so >

Re: [Wireshark-dev] need some more information on bug 8454

On 04/21/13 04:34, Subh. Singh wrote: Hi Jeff, I started looking on bug 8454 . On running wireshark on glibtool I found that some object files are missing. Please see thislog . For some reason that

[Wireshark-dev] [GSoC] Collaboration on JSONShark

Hello. I've become interested in JSONShark project idea and have noticed an earlier post of idea mentor about approx. solution. He says we need more students to work on this project in order to finish it. So I suggest to start collaborating about project subprojects partition, i.e. split a big ide