All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [patch 1/1] netutils: make ping working for confined users
Date: Sat, 19 Feb 2011 06:08:11 +0100	[thread overview]
Message-ID: <1298092091.3101.52.camel@tesla.lan> (raw)
In-Reply-To: <4D5E97DA.50501@redhat.com>

Hello Miroslav !

On Fri, 18/02/2011 at 16.01 +0000, Miroslav Grepl wrote:
> http://mgrepl.fedorapeople.org/F15/admin_netutils.patch
> 
>      * ping did not work for confined users which is fixed by these changes
>      * allow netutils to read network state information and request the 
> kernel to load a module

I have tested ping and traceroute from:

http://www.skbuff.net/iputils/iputils-s20101006.tar.bz2

and they appear to be working fine for confined users with the latest
reference policy (provided that ping is setuid root, which is needed for
opening a raw socket).

Also, I do not suggest that you move files_read_usr_files(traceroute_t)
 further up and away from its "nmap-commented" block. For example, I got
immediately confused, I went looking into traceroute source code and
couldn't find anything that it needs to do with usr files... What would
be very nice there is a boolean for the whole nmap-related block.

Is this series of messages just an acknowledgement of what is being done
on Fedora 15 ? I suppose it is so, as dev_write_usbmon_dev() does not
make sense in refpolicy.

Regards,

Guido

      reply	other threads:[~2011-02-19  5:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 16:01 [refpolicy] [patch 1/1] netutils: make ping working for confined users Miroslav Grepl
2011-02-19  5:08 ` Guido Trentalancia [this message]

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=1298092091.3101.52.camel@tesla.lan \
    --to=guido@trentalancia.com \
    --cc=refpolicy@oss.tresys.com \
    /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.