From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Suraj Upadhyay <usuraj35@gmail.com>
Cc: casey@schauffer-ca.com, kernelnewbies@kernelnewbies.org
Subject: Re: Kernel Project : Implement network interface default labeling for Smack
Date: Tue, 28 Apr 2020 21:08:27 -0400 [thread overview]
Message-ID: <325669.1588122507@turing-police> (raw)
In-Reply-To: <20200428141556.GA10906@blackclown>
[-- Attachment #1.1: Type: text/plain, Size: 1518 bytes --]
On Tue, 28 Apr 2020 19:45:56 +0530, Suraj Upadhyay said:
> I saw a kernel project on kernelnewbies.org [1].
> Which goes like this :-
>
> > Implement network interfce default labeling for Smack.
>
> > Today all unlabeled networking traffic is treated with one
> > "ambient" Smack label. This project consists of taking advantage
> > of mechanisms already in the labeled networking code to allow
> > different labels to be assigned to packets based on the itnerface
> > upon which they appeared.
>
> > Difficulty 5.
>
> I see that the project has not been done yet, as I cannot find any
> described implementation, correct my if I go wrong here.
>
> I really want this to be my first kernel project. I am a relatively
> new comer to the community, and I want to contribute in all my capacity.
Note that this is a lot harder to do correctly than it looks. For starters,
it's not entirely obvious that "label according to interface" is the best
semantic. A better one is probably "based on packet origin" - which gets
interesting now that Wireguard has landed in the kernel. VLANs need to be
considered, and you *definitely* want to re-use the CONFIG_NETWORK_SECMARK code
that AppArmor and SELinux use for network packets. Also, supporting CIPSO would
be pretty much mandatory...
And looking at Documentation/admin-guide/LSM/Smack.rst, it appears that SMACK
is a lot more label-aware than the project description indicates.
In any case, I'm quite sure that Casey will agree with me that "Here There Be Dragons". :)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-04-29 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 14:15 Kernel Project : Implement network interface default labeling for Smack Suraj Upadhyay
2020-04-29 1:08 ` Valdis Klētnieks [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=325669.1588122507@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=casey@schauffer-ca.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=usuraj35@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;
as well as URLs for NNTP newsgroup(s).