CYGWIN=ntsec:[no]strict

[Christopher Faylor <cgf at redhat dot com>]

I was wondering if it would make sense to have cygwin default to
a somewhat looser interpretation of POSIX correctness wrt protections.
I was considering that maybe a file with a .exe, .bat, .cmd extension
should always be considered executable regardless of protection.

It seems like we are consistently confusing people who, after an
install, find that their programs are not considered to be executable by
cygwin.  I'm not sure why this is happening (does someone understand this?)
but it seems like just reverting to the behavior where a file with a .exe
extension is always considred a+x would relieve this problem.

I don't like making this undefeatable however, so I was thinking that
adding a "[no]strict" option to ntsec might be a way to avoid this
behavior.  So, CYGWIN=ntsec:strict would emulate the current behavior
where CYGWIN=ntsec:nostrict (my proposed default) would use the above
indicated behavior.

Is this a stupid idea?

cgf