All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Schewe, Jon     RTX" <jon.schewe@rtx.com>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Filter access to user process sockets
Date: Tue, 30 May 2023 18:21:01 +0000	[thread overview]
Message-ID: <105d714b9a754c4c81063a614ad19517@PH1P110MB1148.NAMP110.PROD.OUTLOOK.COM> (raw)

I have recently learned about using "meta skgid" and "meta skuid" to limit network access based on primary group and user id. I would like to ensure that a user can only connect to sockets where the uid of the running process matches that user. 

Example:
User A starts web server process on port 8000 in 1 shell
User A logs into the same host in another shell. Processes running in this shell should be able to access localhost:8000
User B logs into the same host . Processes running in this shell should be denied access to localhost:8000.

Ideally I'd like to allow the users access to certain common ports under 1024 and any local ports that they create processes on themselves.

Is this something that netfilter can provide? 

Thank you for your time
Jon Schewe


                 reply	other threads:[~2023-05-30 18:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=105d714b9a754c4c81063a614ad19517@PH1P110MB1148.NAMP110.PROD.OUTLOOK.COM \
    --to=jon.schewe@rtx.com \
    --cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.