Features/RemoveSETUID

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Documentation)
(Release Notes)
Line 69: Line 69:
  
 
== Release Notes ==
 
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
+
* '''proposed draft''': Fedora 14 removes setuid applications and instead specifically assigns the capabilities required by an application.
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
+
*
+
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==

Revision as of 20:57, 26 October 2010

Contents

Remove SETUid

Summary

File Capabilties have been present in the Operating System for a few releases now, it is time that we remove setuid applications and just assign the capapilities required by an application. This should make the applications and the Operating System more secure.

Owner

  • Email: <dwalsh@redhat.com>

Current status

Detailed Description

We need to change the spec files of most applications that include a setuid application to remove the setuid flag and change to file capabilities.

Package maintainers after making this change have to verify that their applications still work without the setuid app. In some cases this might not be possible.

Cases where you are and admin becoming root, su, sudo, ksu, userhelper will not be able to change. But I think all package maintainers should take a look at their setuid apps and see if they can do a better, more secure job using file capabilities.

One example, I was able to remove most privs from newrole, now its only capability is the ability to send audit messages.

Benefit to Fedora

This will benefit Fedora by making it more secure.

Scope

Open up a tracker bug, then open a bugzilla on every package that includes setuid applications. We would like to have the Fedora packaging committee codify this in rules and perhaps rpmlint to have smarts about identifying setuid apps and recommending file capabilities.

How To Test

Do a complete install of all Fedora packages and then search for any applications that have the setuid flag. If they do then the Feature is not complete. For any application that was setuid and now uses file capabilities, we need to test that the applications still works as it used to. Test rpmlint on an spec file containing a setuid app, and make sure it prints a proper warning.

User Experience

No change in User Experience should be expected.

Dependencies

We have a dependency that every package that contains a setuid app, is changed by the package owner. Although if we get some/most packages we feel that we have improved the security of the system.

Contingency Plan

None Necessary

Documentation

  • We should change documentation on packaging guidelines to talk about using file capabilities.

Release Notes

  • proposed draft: Fedora 14 removes setuid applications and instead specifically assigns the capabilities required by an application.

Comments and Discussion