From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: crypto flag?
Date: Wed, 07 Dec 2011 19:50:09 +0100 [thread overview]
Message-ID: <1323283809.3404.49.camel@jlt3.sipsolutions.net> (raw)
Hi,
Just wanted to see what people think ... I frequently find myself with
different pcap files:
* OTA files: completely encrypted frames
* locally created files (HW crypto): IV present but frame not encrypted
* (infrequently, with other HW: files that have protection bit w/o IVs)
wireshark has a setting for this, but I find myself switching it around
all the time.
What would you think about a radiotap flag that tells wireshark what
happened in the packet?
johannes
next reply other threads:[~2011-12-07 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 18:50 Johannes Berg [this message]
[not found] ` <1323283809.3404.49.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2011-12-07 19:47 ` crypto flag? Guy Harris
[not found] ` <6561D89F-D6B0-47B6-9DCC-ABDC3BAD9452-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2011-12-07 21:07 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1323283809.3404.49.camel@jlt3.sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).