From: Jeongjun Park <aha310510@gmail.com>
To: paul@paul-moore.com
Cc: aha310510@gmail.com, linux-kernel@vger.kernel.org,
omosnace@redhat.com, selinux@vger.kernel.org,
stephen.smalley.work@gmail.com
Subject: Re: selinux: support IPPROTO_SMC in socket_type_to_security_class()
Date: Fri, 16 Aug 2024 12:57:51 +0900 [thread overview]
Message-ID: <20240816035751.62058-1-aha310510@gmail.com> (raw)
In-Reply-To: <CAHC9VhSrPS27KSG1_On8_WqUfR7tokbrmVwfW3+L_-XJiA=WZw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 2094 bytes --]
Paul Moore wrote:
>
> On Thu, Aug 15, 2024 at 4:32 AM Jeongjun Park <aha310510@gmail.com> wrote:
> >
> > IPPROTO_SMC feature has been added to net/smc. It is now possible to
> > create smc sockets in the following way:
> >
> > /* create v4 smc sock */
> > v4 = socket(AF_INET, SOCK_STREAM, IPPROTO_SMC);
> >
> > /* create v6 smc sock */
> > v6 = socket(AF_INET6, SOCK_STREAM, IPPROTO_SMC);
> >
> > Therefore, we need to add code to support IPPROTO_SMC in
> > socket_type_to_security_class().
> >
> > Signed-off-by: Jeongjun Park <aha310510@gmail.com>
> > ---
> > security/selinux/hooks.c | 2 ++
> > 1 file changed, 2 insertions(+)
>
> I'm a little concerned that the small patch below might not be all
> that is needed to properly support SMC in SELinux. Can you explain
> what testing you've done with SMC on a SELinux system?
I don't have much knowledge about smc, so I can't tested everything, but
I created a socket, performed setsockopt, and tested two sockets
communicating with each other. When I tested it, performing smc-related
functions worked well without any major problems.
And after analyzing it myself, I didn't see any additional patches needed
to support IPPROTO_SMC in selinux other than this patch. So you don't
have to worry.
Regards,
Jeongjun Park
>
> > diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> > index bfa61e005aac..36f951f0c574 100644
> > --- a/security/selinux/hooks.c
> > +++ b/security/selinux/hooks.c
> > @@ -1176,6 +1176,8 @@ static inline u16 socket_type_to_security_class(int family, int type, int protoc
> > return SECCLASS_TCP_SOCKET;
> > else if (extsockclass && protocol == IPPROTO_SCTP)
> > return SECCLASS_SCTP_SOCKET;
> > + else if (extsockclass && protocol == IPPROTO_SMC)
> > + return SECCLASS_SMC_SOCKET;
> > else
> > return SECCLASS_RAWIP_SOCKET;
> > case SOCK_DGRAM:
>
> --
> paul-moore.com
next prev parent reply other threads:[~2024-08-16 3:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 8:32 selinux: support IPPROTO_SMC in socket_type_to_security_class() Jeongjun Park
2024-08-15 16:28 ` Stephen Smalley
2024-08-16 1:46 ` Paul Moore
2024-08-16 3:57 ` Jeongjun Park [this message]
2024-08-16 11:21 ` Stephen Smalley
2024-08-16 11:42 ` Stephen Smalley
2024-08-16 12:53 ` Stephen Smalley
2024-08-19 9:46 ` Ondrej Mosnacek
2024-08-20 18:24 ` Stephen Smalley
2024-08-20 19:51 ` Paul Moore
2024-08-21 13:37 ` Stephen Smalley
2024-08-21 20:01 ` Paul Moore
2024-08-29 13:50 ` Stephen Smalley
2024-08-30 20:04 ` Paul Moore
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=20240816035751.62058-1-aha310510@gmail.com \
--to=aha310510@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
/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