From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
Line 18: Line 18:
== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:dmalcolm| Dave Malcolm]]
* Name: [[User:dmalcolm| Dave Malcolm]]
* Name: [[User:dwalsh| Dan Walsh]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* Email: <dmalcolm@redhat.com>
* Email: <dmalcolm@redhat.com>
* Name: [[User:dwalsh| Dan Walsh]]
* Email: <dwalsh@redhat.com>
* Email: <dwalsh@redhat.com>

Revision as of 19:38, 7 January 2013

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.
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
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed


Friendly EPERM


Coordinated patches to kernel and glibc so that (optionally) strerror(EPERM) gives useful information on why permission was denied


Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: (DATE)
  • Percentage of completion: XX%

Detailed Description

Traditionally, if a process attempts a forbidded operation, errno for that thread is set to EACCES or EPERM, and a call to strerror() returns a localized version of "Permission Denied" or "Operation not permitted". This string appears throughout textual UIs. For example, it will show up in command-line tools, in exceptions within scripting languages, etc.

There are an increasing number of ways in which you can fail to have permission to do something:

  • classic POSIX discretionary access controls
  • Linux security modules (e.g. SELinux mandatory access controls)
  • capabilities
  • etc (TODO: expand this list)

Under normal deployment situations we don't want to leak information to an attacker as to why permission was denied, but under development situations it's useful to know why a failure happens.

We propose to:

  • patch the kernel so that it can optionally provide user-space with a "failure cookie" giving additional information beyond the bare ERRNO (handled at the per-thread level, like strerror, iirc)
  • patch glibc's implementation of strerror (and related calls) so that it can use this "failure cookie" to provide a localized extension to the "Operation not permitted" giving additional details.

The failure cookie would only be exposed to user space for processes with a particular bit set (using prctl), so that you have to opt-in to having this information exposed.


  • cat: /etc/shadow: Permission denied (POSIX: user "david" not owner "root" or in group "root" and file does not have readable-by-all bit)
  • [error] [client ::1] Permission denied (SELinux: context "unconfined_u:system_r:httpd_t:s0" does not have permission to read "system_u:object_r:shadow_t:s0")
  • mount: Permission Denied (Capabilities: user "david" does not have CAP_SYS_ADMIN)

Benefit to Fedora

This feature should significantly simplify debugging permissions issues in Fedora. For example, rather than seeing "Operation not permitted" error and e.g. blindly trying to disable SELinux, a user can see directly whether or not SELinux was involved.


This would require getting a new user-space interface into the kernel, with corresponding changes to the insides of glibc. The precise mechanism has not been decided yet - presumably whatever is acceptable to the upstream kernel/glibc maintainers.

How To Test


User Experience


Contingency Plan


Release Notes

Comments and Discussion