From: David Miller <davem@davemloft.net>
To: mayflowerera@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] macsec: Support XPN frame handling - IEEE 802.1AEbw
Date: Mon, 16 Mar 2020 01:42:47 -0700 (PDT) [thread overview]
Message-ID: <20200316.014247.141724414124911729.davem@davemloft.net> (raw)
In-Reply-To: <20200309194702.117050-1-mayflowerera@gmail.com>
From: Era Mayflower <mayflowerera@gmail.com>
Date: Mon, 9 Mar 2020 19:47:01 +0000
> Support extended packet number cipher suites (802.1AEbw) frames handling.
> This does not include the needed netlink patches.
>
> * Added xpn boolean field to `struct macsec_secy`.
> * Added ssci field to `struct_macsec_tx_sa` (802.1AE figure 10-5).
> * Added ssci field to `struct_macsec_rx_sa` (802.1AE figure 10-5).
> * Added salt field to `struct macsec_key` (802.1AE 10.7 NOTE 1).
> * Created pn_t type for easy access to lower and upper halves.
> * Created salt_t type for easy access to the "ssci" and "pn" parts.
> * Created `macsec_fill_iv_xpn` function to create IV in XPN mode.
> * Support in PN recovery and preliminary replay check in XPN mode.
>
> In addition, according to IEEE 802.1AEbw figure 10-5, the PN of incoming
> frame can be 0 when XPN cipher suite is used, so fixed the function
> `macsec_validate_skb` to fail on PN=0 only if XPN is off.
>
> Signed-off-by: Era Mayflower <mayflowerera@gmail.com>
Applied.
prev parent reply other threads:[~2020-03-16 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 19:47 [PATCH v3 1/2] macsec: Support XPN frame handling - IEEE 802.1AEbw Era Mayflower
2020-03-09 17:52 ` David Miller
2020-03-09 19:47 ` [PATCH v3 2/2] macsec: Netlink support of XPN cipher suites (IEEE 802.1AEbw) Era Mayflower
2020-03-16 8:42 ` David Miller
2020-03-10 23:31 ` [PATCH v3 1/2] macsec: Support XPN frame handling - IEEE 802.1AEbw David Miller
2020-03-16 8:42 ` David Miller [this message]
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=20200316.014247.141724414124911729.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mayflowerera@gmail.com \
--cc=netdev@vger.kernel.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).