Making EPERM friendlier

This sounds like the kind of change that needs to be done with care to avoid introducing new security issues. Crypto code that gives too detailed failure information is often completely broken [1], and I can imagine other places in the kernel where the ability to distinguish reasons for EPERM could be dangerous.

[1] http://en.wikipedia.org/wiki/Padding_oracle_attack