Features/RemoveSETUID

From FedoraProject

< Features
Revision as of 12:40, 25 October 2010 by Dwalsh (Talk | contribs)

Jump to: navigation, search
Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



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

  • Targeted release: Fedora <15>
  • Last updated: (DATE) 2010-10-25
  • Percentage of completion: 10%


Detailed Description

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

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

Comments and Discussion