From: Davide Caratti <dcaratti@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Sabrina Dubroca <sd@queasysnail.net>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: [PATCH net 0/3] macsec: fix configurable ICV length
Date: Fri, 22 Jul 2016 15:07:55 +0200 [thread overview]
Message-ID: <cover.1469191850.git.dcaratti@redhat.com> (raw)
This series provides a fix for macsec configurable ICV length. The
maximum length of ICV element has been made compliant to IEEE 802.1AE,
and error reporting in case of cipher suite configuration failure has been
improved. Finally, a test has been added to netlink verify() callback in
order to avoid creation of macsec interfaces having user-provided ICV length
values that are not supported by the cipher suite.
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
Davide Caratti (3):
macsec: limit ICV length to 16 octets
macsec: fix error codes when a SA is created
macsec: validate ICV length on link creation
drivers/net/macsec.c | 76 ++++++++++++++++++++++++++++--------------
include/uapi/linux/if_macsec.h | 2 ++
2 files changed, 53 insertions(+), 25 deletions(-)
--
2.5.5
next reply other threads:[~2016-07-22 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 13:07 Davide Caratti [this message]
2016-07-22 13:07 ` [PATCH net 1/3] macsec: limit ICV length to 16 octets Davide Caratti
2016-07-22 13:07 ` [PATCH net 2/3] macsec: fix error codes when a SA is created Davide Caratti
2016-07-22 13:07 ` [PATCH net 3/3] macsec: validate ICV length on link creation Davide Caratti
2016-07-25 10:09 ` [PATCH net 0/3] macsec: fix configurable ICV length Sabrina Dubroca
2016-07-25 17:55 ` David Miller
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=cover.1469191850.git.dcaratti@redhat.com \
--to=dcaratti@redhat.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).