From: Suraj Upadhyay <usuraj35@gmail.com>
To: casey@schauffer-ca.com
Cc: kernelnewbies@kernelnewbies.org
Subject: Kernel Project : Implement network interface default labeling for Smack
Date: Tue, 28 Apr 2020 19:45:56 +0530 [thread overview]
Message-ID: <20200428141556.GA10906@blackclown> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]
Hello Casey and List,
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.
Could you please advise me a starting point for this project ?
Like the area of the codebase I need to study before attempting
this.
Any help would be appreciated.
[1] : https://kernelnewbies.org/KernelProjects/SmackInterface
Thanks,
Best wishes,
Suraj Upadhyay
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-04-28 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 14:15 Suraj Upadhyay [this message]
2020-04-29 1:08 ` Kernel Project : Implement network interface default labeling for Smack Valdis Klētnieks
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=20200428141556.GA10906@blackclown \
--to=usuraj35@gmail.com \
--cc=casey@schauffer-ca.com \
--cc=kernelnewbies@kernelnewbies.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).