public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail•com>
To: network dev <netdev@vger•kernel.org>, linux-sctp@vger•kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail•com>,
	Neil Horman <nhorman@tuxdriver•com>,
	davem@davemloft•net
Subject: [PATCH net-next 0/5] sctp: add support for some sctp auth APIs from RFC6458
Date: Wed, 14 Mar 2018 19:05:29 +0800	[thread overview]
Message-ID: <cover.1521025473.git.lucien.xin@gmail.com> (raw)

This patchset mainly adds support for SCTP AUTH Information for sendmsg,
described in RFC6458:

    5.3.8.  SCTP AUTH Information Structure (SCTP_AUTHINFO)

and also adds a sockopt described in RFC6458:

    8.3.4.  Deactivate a Shared Key (SCTP_AUTH_DEACTIVATE_KEY)

and two types of events for AUTHENTICATION_EVENT described in RFC6458:

    6.1.8.  SCTP_AUTHENTICATION_EVENT:
             - SCTP_AUTH_NO_AUTH
             - SCTP_AUTH_FREE_KEY

After this patchset, we have fully support for sctp_sendv in kernel.

Note that this patchset won't touch that sctp options merge conflict.

Xin Long (5):
  sctp: add refcnt support for sh_key
  sctp: add support for SCTP AUTH Information for sendmsg
  sctp: add sockopt SCTP_AUTH_DEACTIVATE_KEY
  sctp: add SCTP_AUTH_FREE_KEY type for AUTHENTICATION_EVENT
  sctp: add SCTP_AUTH_NO_AUTH type for AUTHENTICATION_EVENT

 include/net/sctp/auth.h    |  21 ++++---
 include/net/sctp/command.h |   1 +
 include/net/sctp/sm.h      |   3 +-
 include/net/sctp/structs.h |  10 +++-
 include/uapi/linux/sctp.h  |  22 ++++++-
 net/sctp/auth.c            | 146 +++++++++++++++++++++++++++++++--------------
 net/sctp/chunk.c           |  14 +++++
 net/sctp/output.c          |  18 +++++-
 net/sctp/sm_make_chunk.c   |  33 +++++++++-
 net/sctp/sm_sideeffect.c   |  13 ++++
 net/sctp/sm_statefuns.c    |  56 ++++++++++++++---
 net/sctp/socket.c          |  77 ++++++++++++++++++++++++
 12 files changed, 342 insertions(+), 72 deletions(-)

-- 
2.1.0

             reply	other threads:[~2018-03-14 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 11:05 Xin Long [this message]
2018-03-14 11:05 ` [PATCH net-next 1/5] sctp: add refcnt support for sh_key Xin Long
2018-03-14 13:53   ` Marcelo Ricardo Leitner
2018-03-14 13:59   ` Neil Horman
2018-03-14 16:12     ` Xin Long
2018-03-14 19:41       ` Marcelo Ricardo Leitner
2018-03-14 11:05 ` [PATCH net-next 2/5] sctp: add support for SCTP AUTH Information for sendmsg Xin Long
2018-03-14 13:53   ` Marcelo Ricardo Leitner
2018-03-14 11:05 ` [PATCH net-next 3/5] sctp: add sockopt SCTP_AUTH_DEACTIVATE_KEY Xin Long
2018-03-14 13:53   ` Marcelo Ricardo Leitner
2018-03-14 11:05 ` [PATCH net-next 4/5] sctp: add SCTP_AUTH_FREE_KEY type for AUTHENTICATION_EVENT Xin Long
2018-03-14 13:53   ` Marcelo Ricardo Leitner
2018-03-14 11:05 ` [PATCH net-next 5/5] sctp: add SCTP_AUTH_NO_AUTH " Xin Long
2018-03-14 13:53   ` Marcelo Ricardo Leitner
2018-03-14 17:49 ` [PATCH net-next 0/5] sctp: add support for some sctp auth APIs from RFC6458 David Miller
2018-03-15 13:20 ` Neil Horman

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.1521025473.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-sctp@vger$(echo .)kernel.org \
    --cc=marcelo.leitner@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=nhorman@tuxdriver$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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