From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, selinux@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-sctp@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
marcelo.leitner@gmail.com, jmorris@namei.org,
paul@paul-moore.com, richard_c_haines@btinternet.com,
omosnace@redhat.com
Subject: Re: [PATCHv2 net 0/4] security: fixups for the security hooks in sctp
Date: Wed, 03 Nov 2021 11:20:09 +0000 [thread overview]
Message-ID: <163593840902.17756.9280314114933444317.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1635854268.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 2 Nov 2021 08:02:46 -0400 you wrote:
> There are a couple of problems in the currect security hooks in sctp:
>
> 1. The hooks incorrectly treat sctp_endpoint in SCTP as request_sock in
> TCP, while it's in fact no more than an extension of the sock, and
> represents the local host. It is created when sock is created, not
> when a conn request comes. sctp_association is actually the correct
> one to represent the connection, and created when a conn request
> arrives.
>
> [...]
Here is the summary with links:
- [PATCHv2,net,1/4] security: pass asoc to sctp_assoc_request and sctp_sk_clone
https://git.kernel.org/netdev/net/c/c081d53f97a1
- [PATCHv2,net,2/4] security: call security_sctp_assoc_request in sctp_sf_do_5_1D_ce
https://git.kernel.org/netdev/net/c/e215dab1c490
- [PATCHv2,net,3/4] security: add sctp_assoc_established hook
https://git.kernel.org/netdev/net/c/7c2ef0240e6a
- [PATCHv2,net,4/4] security: implement sctp_assoc_established hook in selinux
https://git.kernel.org/netdev/net/c/e7310c94024c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-11-03 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 12:02 [PATCHv2 net 0/4] security: fixups for the security hooks in sctp Xin Long
2021-11-02 12:02 ` [PATCHv2 net 1/4] security: pass asoc to sctp_assoc_request and sctp_sk_clone Xin Long
2021-11-02 12:02 ` [PATCHv2 net 2/4] security: call security_sctp_assoc_request in sctp_sf_do_5_1D_ce Xin Long
2021-11-02 12:02 ` [PATCHv2 net 3/4] security: add sctp_assoc_established hook Xin Long
2021-11-02 12:02 ` [PATCHv2 net 4/4] security: implement sctp_assoc_established hook in selinux Xin Long
2021-11-03 16:40 ` Ondrej Mosnacek
2021-11-03 17:33 ` Xin Long
2021-11-03 17:36 ` Xin Long
2021-11-03 22:01 ` Paul Moore
2021-11-04 1:46 ` Xin Long
2021-11-04 3:17 ` Paul Moore
2021-11-04 10:17 ` Richard Haines
2021-11-04 10:40 ` Ondrej Mosnacek
2021-11-04 19:28 ` Paul Moore
2021-11-04 10:56 ` Xin Long
2021-11-04 11:02 ` David Miller
2021-11-04 19:10 ` Paul Moore
2021-11-04 19:49 ` Xin Long
2021-11-04 20:07 ` Paul Moore
2021-11-03 11:20 ` patchwork-bot+netdevbpf [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=163593840902.17756.9280314114933444317.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@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).