All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [ SEMANAGE ] Add a few direct dbases to handle
Date: Fri, 14 Oct 2005 16:20:46 -0400	[thread overview]
Message-ID: <4350131E.8060708@tresys.com> (raw)
In-Reply-To: <434FF612.8010708@cornell.edu>

Ivan Gyurdiev wrote:
> Adds a few direct databases to the handle.
> There's still no dangerous code in the main commit path...
> This is just the equivalent to file init.
> 
> diff -Naur libsemanage/src/handle.h libsemanage.new/src/handle.h
> --- libsemanage/src/handle.h	2005-10-14 14:10:54.000000000 -0400
> +++ libsemanage.new/src/handle.h	2005-10-14 14:07:46.000000000 -0400
> @@ -71,12 +71,20 @@
>  	struct semanage_policy_table* funcs;
>  
>  	/* Object databases */
> -#define DBASE_COUNT      5
> +#define DBASE_COUNT      7
> +
>  #define DBASE_USERS      0
>  #define DBASE_PORTS      1
>  #define DBASE_INTERFACES 2
>  #define DBASE_BOOLEANS   3
>  #define DBASE_SEUSERS    4
> +
> +#define DBASE_BASE_USERS      5
> +#define DBASE_BASE_PORTS      6
> +#if 0
> +#define DBASE_BASE_INTERFACES 7
> +#define DBASE_BASE_BOOLEANS   8
> +#endif
>  	dbase_config_t dbase[DBASE_COUNT];
>  };
>  
> @@ -105,5 +113,27 @@
>  	return &handle->dbase[DBASE_SEUSERS];
>  }
>  

I thought we agreed to have a direct only accessible part of the handle, 
  such as

struct semanage_direct_handle {
	semanage_handle_t *handle;
	/* direct stuff goes here */
};

So that this stuff is only exposed to direct api functions? The policy 
server shouldn't be filling out databases that are accessible to the 
user since it needs to mediate access.

Joshua


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2005-10-14 20:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 18:16 [ SEMANAGE ] Add a few direct dbases to handle Ivan Gyurdiev
2005-10-14 18:39 ` [ SEMANAGE ] Bugfix previous patches Ivan Gyurdiev
2005-10-14 20:08   ` Stephen Smalley
2005-10-14 20:20 ` Joshua Brindle [this message]
2005-10-14 20:40   ` [ SEMANAGE ] Add a few direct dbases to handle Ivan Gyurdiev
2005-10-14 20:45     ` Ivan Gyurdiev
2005-10-14 20:39       ` Joshua Brindle
2005-10-14 20:59         ` Ivan Gyurdiev
2005-10-14 21:06           ` Joshua Brindle
2005-10-14 21:40             ` Ivan Gyurdiev
2005-10-15 11:34               ` Ivan Gyurdiev
2005-10-15 11:38                 ` Ivan Gyurdiev

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=4350131E.8060708@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=ivg2@cornell.edu \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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.