linux-kernel - Re: usbmon: size of different fields?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101110082123.2dc1d361@lembas.zaitcev.lan>
Date:	Wed, 10 Nov 2010 08:21:23 -0700
From:	Pete Zaitcev <zaitcev@...hat.com>
To:	Guy Harris <guy@...m.mit.edu>
Cc:	Developer support list for Wireshark 
	<wireshark-dev@...eshark.org>, linux-usb@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: usbmon: size of different fields?

On Tue, 9 Nov 2010 13:23:28 -0800
Guy Harris <guy@...m.mit.edu> wrote:
> On Nov 9, 2010, at 12:05 PM, Németh Márton wrote:
> 
> > OK, that's clear, the byte order of the API structure fields are in "host endian"
> > order. The API structures are already saved by Wireshark into file for quite some
> > time.
> 
> ...and tcpdump.  Support for capturing on USB on Linux has been in
> libpcap since at least libpcap 1.0.

I imagined that Nemeth wanted to implement an alternative to that.
Surely he knows how libpcap works. In that case a new, host-independent
format may be introduced. But userland is mysterious to me.

I'll make sure to document ISO descriptors properly. I was sure
I had done that, sorry.

-- Pete
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/