From Fedora Project Wiki
No edit summary
No edit summary
Line 1: Line 1:
= Remove SETUid <!-- The name of your feature --> =
= Remove SETUid <!-- The name of your feature --> =


Line 16: Line 15:
* Last updated: (DATE) 2010-10-25
* Last updated: (DATE) 2010-10-25
* Percentage of completion: 10%
* Percentage of completion: 10%
* Tracker Bug https://bugzilla.redhat.com/show_bug.cgi?id=646440 added


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->

Revision as of 17:10, 25 October 2010

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