Re: [Wireshark-users] Need wireshark 0.99.7
Hi Jason, How to compile that downloaded SVN? After downloading what are the steps I have to perform to install wireshark 0.99.7 in Linux environment Saravanan BV On 10/25/07, DePriest, Jason R. <[EMAIL PROTECTED]> wrote: > > On 10/25/07, DePriest, Jason R. <> wrote: > > On 10/24/07, Saravanan BV wrote: > > > Hi all, > > > > > > I need wireshark 0.99.7 for fedora core 6. Where to download that. > In all > > > the download i am gettting only wireshark 0.99.6. > > > Help me for wireshark 0.99.7. > > > > > > Thanks and regards, > > > SARAVANAN BV > > > > I don't think 0.99.7 is released yet. You can download the source > > from SVN and compile it I guess. > > > > -Jason > > > > Or check the Wireshark website and discover this > > Download A Development Release > Source code packages and Windows installers are automatically created > each time code is checked into the source code repository. These > packages are available in the automated build section > (http://www.wireshark.org/download/automated/) of our download area. > > like I just did. > > You can download the latest SVN version of 0.99.7, but there aren't > any RPMs hosted. So you'd still have to compile, but at least you > could skip the SVN setup. > > -Jason > > -Jason > ___ > Wireshark-users mailing list > Wireshark-users@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-users > ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Need wireshark 0.99.7
On 10/25/07, DePriest, Jason R. <> wrote: > On 10/24/07, Saravanan BV wrote: > > Hi all, > > > > I need wireshark 0.99.7 for fedora core 6. Where to download that. In all > > the download i am gettting only wireshark 0.99.6. > > Help me for wireshark 0.99.7. > > > > Thanks and regards, > > SARAVANAN BV > > I don't think 0.99.7 is released yet. You can download the source > from SVN and compile it I guess. > > -Jason > Or check the Wireshark website and discover this Download A Development Release Source code packages and Windows installers are automatically created each time code is checked into the source code repository. These packages are available in the automated build section (http://www.wireshark.org/download/automated/) of our download area. like I just did. You can download the latest SVN version of 0.99.7, but there aren't any RPMs hosted. So you'd still have to compile, but at least you could skip the SVN setup. -Jason -Jason ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Need wireshark 0.99.7
On 10/24/07, Saravanan BV wrote: > Hi all, > > I need wireshark 0.99.7 for fedora core 6. Where to download that. In all > the download i am gettting only wireshark 0.99.6. > Help me for wireshark 0.99.7. > > Thanks and regards, > SARAVANAN BV I don't think 0.99.7 is released yet. You can download the source from SVN and compile it I guess. -Jason ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
[Wireshark-users] Need wireshark 0.99.7
Hi all, I need wireshark 0.99.7 for fedora core 6. Where to download that. In all the download i am gettting only wireshark 0.99.6. Help me for wireshark 0.99.7. Thanks and regards, SARAVANAN BV ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid default filenames
On Wed, Oct 24, 2007 at 07:30:05PM +0200, Luis EG Ontanon wrote: > BTW url-encoding filenames would be a solution for this kind of > isues... guess what urlencoding was thought for exactly that! > > filename%20with%20spaces.ext I was hoping that GLib would have functions to handle this, but it does not from what I can find. Do you know of any GPL compatible code that does this that we could borrow? Does wget transform URLs to that url encoding method? Steve ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid default filenames
> -Original Message- > From: Guy Harris > Sent: Wednesday, October 24, 2007 11:23 AM > > Mark G. wrote: > > > But for those of us who are using Wireshark to leech large > > numbers of images from a commercial web site, the incremental > > naming feature would be very helpful. ;-) > > Isn't that what programs such as curl and wget are for? Using Wireshark > seems a bit indirect, especially given that somebody has to be fetching > the file *anyway* in order for Wireshark to see the traffic. If I could construct the URLs to obtain the images, then I would certainly use a different tool to fetch the data. But I can't. I need to interact with the web site to fetch the images. The web site uses a proprietary viewer which does not appear to cache the images after they are downloaded. So I am using Wireshark extract the images from the data stream. -Mark ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid defaultfilenames
Mark G. wrote: > But for those of us who are using Wireshark to leech large > numbers of images from a commercial web site, the incremental > naming feature would be very helpful. ;-) Isn't that what programs such as curl and wget are for? Using Wireshark seems a bit indirect, especially given that somebody has to be fetching the file *anyway* in order for Wireshark to see the traffic. ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid defaultfilenames
> -Original Message- > From: Luis EG Ontanon > Sent: Wednesday, October 24, 2007 10:30 AM > > BTW url-encoding filenames would be a solution for this kind of > isues... guess what urlencoding was thought for exactly that! > > filename%20with%20spaces.ext True enough. But for those of us who are using Wireshark to leech large numbers of images from a commercial web site, the incremental naming feature would be very helpful. ;-) -Mark ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid default filenames
Luis EG Ontanon wrote: > in *NIX filenames with spaces are particularly tedious... I > personally would forbid spaces in filenames en-toto as they tend to > make scripts fail... Well, insufficiently-carefully-written scripts, anyway. $ echo a b > a\ b $ echo c d > c\ d $ find . -type f -print0 | xargs -0 grep a /dev/null ./a b:a b I don't know whether all systems have the "-print0" flag to find (makes it terminate the file names it prints with a null byte rather than with a newline) and the "-0" flag to xargs (makes it expect file names terminated with a null byte), but that handles file names with spaces in them - and also handles a resulting file list bigger than the maximum number of arguments that can be passed in an exec call. (The /dev/null also makes sure there are at least two arguments to grep, so it always reports the file name.) This is also a potential issue on Windows, if, for example, you're using a UN*X shell (I don't know whether you have to be careful when writing .bat files to make sure *they* handle file names with spaces in them). Yes, file names with spaces are a bit more inconvenient to use from command lines (UN*X or Windows), but command-line support has gotten better over time (file name completion handles it in bash and the version of ksh in Leopard, at least, and options such as -print0 to find have shown up over time), and they aren't particularly inconvenient from a GUI. We might still want to, e.g. replace them with underscores, or have an option to allow them to be replaced with underscores. ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid default filenames
BTW url-encoding filenames would be a solution for this kind of isues... guess what urlencoding was thought for exactly that! filename%20with%20spaces.ext On 10/24/07, Jeff Morriss <[EMAIL PROTECTED]> wrote: > > > Luis EG Ontanon wrote: > > On 10/24/07, Jeff Morriss <[EMAIL PROTECTED]> wrote: > >> Since it's primarily Windows that should have this problem (AFAICR most > >> *NIXs allow anything other than "/" in a file name) it should be easy > >> enough to find a list of prohibited chars. > > > > in *NIX filenames with spaces are particularly tedious... I > > personally would forbid spaces in filenames en-toto as they tend to > > make scripts fail... > > Haha, a friend of mine used to keep a program around whose file name was > " " (just a space) to confound *NIX newbies. (I can't remember if the > program did anything interesting or not.) > > More seriously, though, those working inside some desktop environment > (like GNOME) don't have to worry about what's in file names since the > environment takes care of making sure the file names are handled > appropriately. > > (Your preference does make an argument to have the list of > chars-banned-from-file-names configurable though in thinking more about > it now I'm not sure where such a preference would be.) > ___ > 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] Exporting objects with invalid default filenames
Luis EG Ontanon wrote: > On 10/24/07, Jeff Morriss <[EMAIL PROTECTED]> wrote: >> Since it's primarily Windows that should have this problem (AFAICR most >> *NIXs allow anything other than "/" in a file name) it should be easy >> enough to find a list of prohibited chars. > > in *NIX filenames with spaces are particularly tedious... I > personally would forbid spaces in filenames en-toto as they tend to > make scripts fail... Haha, a friend of mine used to keep a program around whose file name was " " (just a space) to confound *NIX newbies. (I can't remember if the program did anything interesting or not.) More seriously, though, those working inside some desktop environment (like GNOME) don't have to worry about what's in file names since the environment takes care of making sure the file names are handled appropriately. (Your preference does make an argument to have the list of chars-banned-from-file-names configurable though in thinking more about it now I'm not sure where such a preference would be.) ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Configure problem with pcap_open_live
Paulo Wilbert wrote: > Resulting config.log was attached. > > libpcap-0.9.8 was installed (at least ./configure, make and make install > did not show errors). (That was done on Linux, so you could probably have installed a binary package for libpcap and the corresponding developer package, if there's a separate developer package. In fact, the binary package might already be installed, if, for example, you have a /usr/lib/libpcap.so file, in which case you should probably un-install libpcap 0.9.8 and install the distribution's developer package, unless you explicitly want to use 0.9.8 built from source rather than what comes with the distribution.) If you run "ranlib /usr/local/lib/libpcap.a", does that fix things? ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid default filenames
On 10/24/07, Jeff Morriss <[EMAIL PROTECTED]> wrote: > Since it's primarily Windows that should have this problem (AFAICR most > *NIXs allow anything other than "/" in a file name) it should be easy > enough to find a list of prohibited chars. in *NIX filenames with spaces are particularly tedious... I personally would forbid spaces in filenames en-toto as they tend to make scripts fail... [id-est:~/tt] lego% echo a b > a\ b [id-est:~/tt] lego% echo c d > c\ d [id-est:~/tt] lego% head * ==> a b <== a b ==> c d <== c d [id-est:~/tt] lego% find . -type f ./a b ./c d [id-est:~/tt] lego% grep a `find . -type f` grep: ./a: No such file or directory grep: b: No such file or directory grep: ./c: No such file or directory grep: d: No such file or directory -- 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] K12 capture file problems
Luis EG Ontanon <[EMAIL PROTECTED]> writes: > And the "ETHER" issue which you should explain better what's about, > because I honestly didn't understand it. Bug #1937. ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid default filenames
Jeff Morriss wrote: > Mark G. wrote: > >>> -Original Message- >>> From: Stephen Fisher >>> Sent: Tuesday, October 23, 2007 8:29 PM >>> >>> I could not think of a really good way to handle these >>> filenames thatare unsavable when I implemeneted the export >>> object feature. Were you hoping to save all of the objects >>> with filenames that increment or just the ones that are >>> based on HTTP GET requests that cannot be saved with >>> their HTTP GET filenames? >>> >> Either way would work. I think it would be simpler and >> more intuitive to only use an incremental filename when >> the exporter encounters a file with an invalid default >> filename. I think an _ideal_ implementation would be to >> provide a checkbox enabling the user to specify whether >> he wants all exported objects to use the incremental >> filename, or only the objects whose default filenames >> are invalid. >> > > Grip (a CD ripper for Linux/*NIX) has a configuration item that lists > characters that it is not allowed to put into file names--if any of > those letters appear then it deletes them (or replaces them with a space?). > > Since it's primarily Windows that should have this problem (AFAICR most > *NIXs allow anything other than "/" in a file name) it should be easy > enough to find a list of prohibited chars. > > That would result in file names as close to the original as possible. > ___ > In W2K or later, there is the API call PathCleanupSpec() (http://msdn2.microsoft.com/en-us/library/bb776472.aspx) that will remove invalid characters according to the rules specified for the target filesystem. -- Regards, Graham Bloice ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invalid default filenames
Mark G. wrote: >> -Original Message- >> From: Stephen Fisher >> Sent: Tuesday, October 23, 2007 8:29 PM >> >> I could not think of a really good way to handle these >> filenames thatare unsavable when I implemeneted the export >> object feature. Were you hoping to save all of the objects >> with filenames that increment or just the ones that are >> based on HTTP GET requests that cannot be saved with >> their HTTP GET filenames? > > Either way would work. I think it would be simpler and > more intuitive to only use an incremental filename when > the exporter encounters a file with an invalid default > filename. I think an _ideal_ implementation would be to > provide a checkbox enabling the user to specify whether > he wants all exported objects to use the incremental > filename, or only the objects whose default filenames > are invalid. Grip (a CD ripper for Linux/*NIX) has a configuration item that lists characters that it is not allowed to put into file names--if any of those letters appear then it deletes them (or replaces them with a space?). Since it's primarily Windows that should have this problem (AFAICR most *NIXs allow anything other than "/" in a file name) it should be easy enough to find a list of prohibited chars. That would result in file names as close to the original as possible. ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Exporting objects with invaliddefault filenames
> -Original Message- > From: Stephen Fisher > Sent: Tuesday, October 23, 2007 8:29 PM > > I could not think of a really good way to handle these > filenames thatare unsavable when I implemeneted the export > object feature. Were you hoping to save all of the objects > with filenames that increment or just the ones that are > based on HTTP GET requests that cannot be saved with > their HTTP GET filenames? Either way would work. I think it would be simpler and more intuitive to only use an incremental filename when the exporter encounters a file with an invalid default filename. I think an _ideal_ implementation would be to provide a checkbox enabling the user to specify whether he wants all exported objects to use the incremental filename, or only the objects whose default filenames are invalid. > > Do you have any other ideas of a good way to fix this? > Maybe letting the user click on the filename field and > change the ones they want to? > That would be one way to do it. But this could also become tedious, if the file list is long. And of course the user may not be able to identify all of the invalid filenames until the exporter complains about them. Another approach would be to allow the user to enter a filespec consisting of a base filename and wildcards that would be replaced by an incremental number. In my current project for example, I am downloading a large number of JPEG2000 files. So I might enter the following filespec to be used for all objects with invalid default filenames: IMAGE.JP2 As the exporter encounters objects with invalid filenames, it will name them IMAGE0001.JP2, IMAGE0002.JP2, and so on. BTW, Wireshark is a _most_ excellent product. This feature would make it even _more_ excellent (for me, at least. :-) Thanks -Mark ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] K12 capture file problems
On 10/24/07, Magnus Homann <[EMAIL PROTECTED]> wrote: > I have two things about the K12 capture file format, that seems to be bugs: > 1) Saving as K12 saves as using 'ETHER' as protocol instead of 'ETHERNET'. > Wireshark can not read its own files, unless you change it to 'ETHERNET' > 2) It appears to me that the K12 capture file must be minimum 8K or so for > Wireshark to read it. > > Is any of this a known problem, or else I'll report is as bugs. That's two Bugs: please attach example files (eventually make the atachments private), and describe how to reproduce the problem thanks the 8K thing that I can imagine its cause... although I do not understand how did it passed the regression (there's more <8K files in my test pool). However if you have a file <8K that you cannot read please add it to the bug. And the "ETHER" issue which you should explain better what's about, because I honestly didn't understand it. Luis -- 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
[Wireshark-users] K12 capture file problems
I have two things about the K12 capture file format, that seems to be bugs: 1) Saving as K12 saves as using 'ETHER' as protocol instead of 'ETHERNET'. Wireshark can not read its own files, unless you change it to 'ETHERNET' 2) It appears to me that the K12 capture file must be minimum 8K or so for Wireshark to read it. Is any of this a known problem, or else I'll report is as bugs. Magnus ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
