public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roberto De Ioris <roberto@unbit.it>
To: Gerhard Mack <gmack@innerfire.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] UidBind LSM 0.1
Date: Mon, 23 Apr 2007 23:04:59 +0200	[thread overview]
Message-ID: <1177362299.20613.28.camel@hagrid> (raw)
In-Reply-To: <Pine.LNX.4.64.0704231435430.15351@mtl.rackplans.net>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

Il giorno lun, 23/04/2007 alle 14.38 -0400, Gerhard Mack ha scritto:
> On Mon, 23 Apr 2007, Roberto De Ioris wrote:
> > Hi all,
> > this is a very simple module that allows bind() to tcp/udp port (>=1024)
> > only for the uids defined in a configfs tree.
> > 
> > It is a first version, it only works for PF_INET sockets and makes no
> > difference between tcp and udp (i am working on this)
> > 
> > For (little) more info see 
> > 
> > http://projects.unbit.it/uidbind/
> > 
> > Patch attached is for vanilla 2.6.20.7
> 
> Is it possible to lock a range of ports to a uid?  

I think i can implement something like a configfs item named
'8081-8090', instead of only '8081'.
I will need to validate the range, but its not too difficult.

> 
> Also, is it possible to lock a uid to one ip address?  For example usera 
> can only bind to 10.0.0.23 while userb can only bind to 10.0.0.24. 

This is simple to add and i have already a patch for it.
In the next few days i will post it.


-- 
Roberto De Ioris
http://unbit.it
JID: roberto@jabber.unbit.it
Wii: 2999 4476 3509 0964

[-- Attachment #2: Questa è una parte del messaggio firmata digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-04-23 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23  8:54 [ANNOUNCE] UidBind LSM 0.1 Roberto De Ioris
2007-04-23 18:38 ` Gerhard Mack
2007-04-23 21:04   ` Roberto De Ioris [this message]
2007-04-24 13:51 ` Casey Schaufler
2007-04-24 14:01   ` Roberto De Ioris

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=1177362299.20613.28.camel@hagrid \
    --to=roberto@unbit.it \
    --cc=gmack@innerfire.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox