Corinna Vinschen wrote: > Sorry Brian, but this has only marginally to do with integrity levels. > The real reason for this is the SeCreateGlobalPrivilege introduced with > Windows 2003. Only administrative users hold this privilege by default,
Right, I wasn't trying to imply that the location of the shared section had anything to do with IL, just explaining why his elevated shell in session 1 could see the processes of services in session 0 (i.e. because the elevated session 1 could create the shared section in the global namespace and read the cygwin process table.) Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
