From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org
Subject: [RFC] decryption flags
Date: Wed, 21 Oct 2015 13:22:10 +0200 [thread overview]
Message-ID: <1445426530.4558.28.camel@sipsolutions.net> (raw)
I'd like to define decryption flags, to indicate
* frame was decrypted (FC protected bit is set, but data is decrypted)
* in this case - (ext)IV is present
* in this case - MIC isn't present
Wireshark can be configured for the first two (and cannot currently
deal with the third at all), but it's tedious to configure it according
to the capture file you happen to have at hand.
I suggest to define the following field:
= extended flags =
Bit Number:: 22 (not assigned yet)
Structure:: u32 flags
Required Alignment:: 4
Unit(s):: n/a
This field defines decryption flags for frames. The following flags are
defined:
|| '''value''' || '''meaning''' ||
|| `0x00000001` || frame is decrypted (but FC protected bit is set) ||
|| `0x00000002` || frame is encrypted (FC protected bit is also set) ||
|| `0x00000004` || (ext) IV is still present (reserved if 0x1 isn't set) ||
|| `0x00000008` || MIC is not present (should only be used if FCS is also not present, reserved if 0x1 isn't set) ||
|| `0xfffffff0` || (reserved) ||
If there are no objections I'll work on a wireshark patch (though
probably only in about two weeks from now, since I'll be travelling)
johannes
next reply other threads:[~2015-10-21 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 11:22 Johannes Berg [this message]
[not found] ` <1445426530.4558.28.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-10-21 11:23 ` [RFC] decryption flags 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=1445426530.4558.28.camel@sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-S783fYmB3Ccdnm+yROfE0A@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).