mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][PATCH] New fs to control access to system resources
Date: Tue, 15 Jan 2002 09:53:47 -0700	[thread overview]
Message-ID: <200201151653.g0FGrlG12428@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <87k7uj61tk.fsf@tigram.bogus.local>
In-Reply-To: <87k7uj61tk.fsf@tigram.bogus.local>

Olaf Dietsche writes:
> --=-=-=
> 
> Hi,
> 
> this is a new file system to control access to system resources.
> Currently it controls access to inet_bind() with ports < 1024 only.
> 
> With this patch, there's no need anymore to run internet daemons as
> root. You can individually configure which user/program can bind to
> ports below 1024.
> 
> For example, you can say, user www is allowed to bind to port 80 or
> user mail is allowed to bind to port 25. Then, you can run apache as
> user www and sendmail as user mail. Now, you don't have to rely on
> apache or sendmail giving up superuser rights to enhance security.
> 
> To use this, you need to mount the file system and do a chown on the
> appropriate ports:
> 
> # mount -t accessfs none /mnt
> # chown www /mnt/net/ipv4/bind/80
> # chown mail /mnt/net/ipv4/bind/25

Having to set the permissions like this on each boot seems a bit
painful. Why not have permissions persistence like devfs has?

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2002-01-15 16:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 16:01 Olaf Dietsche
2002-01-15 16:53 ` Richard Gooch [this message]
2002-01-15 17:38   ` Wichert Akkerman
2002-01-15 17:48   ` Olaf Dietsche
2002-01-15 17:54   ` Richard Gooch
2002-01-16 19:05   ` Andreas Ferber
2002-01-15 22:13 ` Ben Clifford
2002-01-15 22:24   ` Measuring execution time Mark Cuss
2002-01-16 17:23     ` Chris Friesen
2002-01-16 17:53       ` Richard B. Johnson
2002-01-16 21:47       ` Jakob Østergaard
2002-01-16 17:18   ` [ANNOUNCE][PATCH] New fs to control access to system resources Olaf Dietsche
2002-01-16 18:26     ` Ben Clifford
2002-01-17  0:34       ` Olaf Dietsche
2002-01-15 22:51 ` CaT
2002-01-15 23:00   ` David Weinehall
2002-01-15 23:13     ` CaT
2002-01-16  4:19 ` dean gaudet
2002-01-16 17:18   ` Olaf Dietsche
2002-01-16 18:12     ` dean gaudet
2002-01-17  0:34       ` Olaf Dietsche
2002-01-16 18:51 ` Andreas Ferber
2002-01-16 13:38   ` gmack
2002-01-16 23:06   ` Greg KH
2002-01-17  9:26     ` Andreas Ferber
2002-01-18 19:38       ` Greg KH
2002-01-18 15:36 ` Anthony DeRobertis
2002-01-18 18:22   ` Olaf Dietsche

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=200201151653.g0FGrlG12428@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf.dietsche--list.linux-kernel@exmail.de \
    /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

all inboxes | Powered by JetHome®