All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	selinux@tycho.nsa.gov,
	Manoj Srivastava <manoj.srivastava@stdc.com>
Subject: Re: ANN:  Updated SELinux core userland release
Date: Wed, 26 Sep 2007 10:59:24 -0400	[thread overview]
Message-ID: <46FA73CC.60907@redhat.com> (raw)
In-Reply-To: <1190815607.1812.27.camel@gorn.columbia.tresys.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christopher J. PeBenito wrote:
> On Wed, 2007-09-26 at 09:25 -0400, Stephen Smalley wrote:
>> On Wed, 2007-09-26 at 13:03 +0000, Christopher J. PeBenito wrote:
>>> On Tue, 2007-09-25 at 15:55 -0400, Stephen Smalley wrote:
>>>> An updated release of the SELinux core userland code is available from
>>>> the NSA web site, see:
>>>> http://www.nsa.gov/selinux/news.cfm#R070925
>>>>
>>>> Updated versions of the stable and development (trunk) series can be
>>>> downloaded from:
>>>> http://www.nsa.gov/selinux/code/
>>>>
>>>> For those who use the sourceforge svn tree, the stable branch and trunk
>>>> have been tagged as 20070925 under tags/stable and tags/devel
>>>> respectively for this release.
>>>>
>>>> It would be useful to know if anyone is using the stable branch; it was
>>>> created for use by users and distributions that want maximal stability
>>>> (bug fixes and trivial code cleanups only), e.g. to provide updates to
>>>> an existing distribution release like Debian etch or Fedora Core 6 or
>>>> RHEL 5 without risking the potentially more disruptive changes from the
>>>> trunk/devel series.  However, I  haven't gotten the impression that it
>>>> is being actively used.
>>> Gentoo uses the stable branch, and currently doesn't have plans to use
>>> 2.0.
>> Ok, maybe you can help give feedback then on what if any features you'd
>> like to see back ported from the trunk to the stable branch.  Examples
>> of things that are only presently in the 2.x series include:
> 
>> - disable dontaudit support in semodule and the libraries,
> 
> If nothing else, this would be choice.  And/or the unknown perms
> handling.
> 
>> - refactored swig bindings for libselinux
> 
> If this fixes bugs in the current bindings, that'd be good choice too.
> 
Red Hat basically freezes the release, and then apply patches only
sparingly to the release.  We do not usually backport major
functionality changes to previous releases.  So change like removal of
genhomedircon are considered to dangerous for RHEL.  (Although semodule
- -DB would be nice.)

Rawhide/F8 are built off trunk.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFG+nPLrlYvE4MpobMRAgB9AKCFbsh9OxHD7bzMs1QO7zTLx/v0CwCfUm99
P3r3DntvXnkbjBZF6yaGUmo=
=xNIU
-----END PGP SIGNATURE-----

--
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.

  reply	other threads:[~2007-09-26 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 20:04 ANN: Updated SELinux core userland release Stephen Smalley
2007-09-25 19:55 ` Stephen Smalley
2007-09-26 13:03   ` Christopher J. PeBenito
2007-09-26 13:25     ` Stephen Smalley
2007-09-26 14:06       ` Christopher J. PeBenito
2007-09-26 14:59         ` Daniel J Walsh [this message]
2007-09-27 13:35         ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2008-03-05 20:56 Stephen Smalley
2008-06-11 18:51 Stephen Smalley

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=46FA73CC.60907@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cpebenito@tresys.com \
    --cc=manoj.srivastava@stdc.com \
    --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.