From: Roy Sigurd Karlsbakk <roy@fast.no>
To: linux-kernel mailinglist <linux-kernel@vger.kernel.org>
Subject: Restricting available ports
Date: Wed, 11 Apr 2001 11:13:05 +0200 [thread overview]
Message-ID: <3AD42021.5DF9CA62@fast.no> (raw)
Hi all
A friend of mine asked me how he could restrict which ports a given user
should be allowed to open. He's running a shell server people use for
IRC bots. I don't think this is possible today. Is it possible to build
it without ruining the whole system? Like a kernel module?
Please cc: to me, as I'm not on the list
Regards
roy
reply other threads:[~2001-04-11 9:12 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=3AD42021.5DF9CA62@fast.no \
--to=roy@fast.no \
--cc=linux-kernel@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.