Capabilities by any other name

Douglas Crockford crock@communities.com
Tue, 9 Nov 1999 11:30:54 -0800


> > Stop using "capabilities" except when preceded by "historically, ".
>
> This isn't the right answer either.  Too much of the serious security
> community groks capabilities correctly, so ceding the term to the POSIX
> folks isn't a good thing to do.

Too much? Too much?

I want to see this stuff go mainstream. If you guys are not planning on
going mainstream, then please take me off the list.

The issue isn't POSIX. The issue is the word "capabilities". It is
overloaded and confusing.

You confuse, you lose.