Posix, Cygwin and Security (oh my? heh)

From: simonis (simonis@myself.com)
Date: 11/12/02 

From: simonis <simonis@myself.com>
Date: Tue, 12 Nov 2002 18:34:55 GMT

All,
I have a question regarding the Cygwin.dll that some of us use
on our Windows system. My issue is with the security reasoning
behind removing the Posix subsystem. I know that this is a
"best practice" and eliminates an issue with duplicate file naming
but I'm not sure that either of these are a good reason. Any pointers
as to the reasoning?

But to the issue... does adding in the cygwin.dll simply shift the
security issues with posix to a new dll?

-Ds

Relevant Pages

  • Re: Scott & Andrei article on DCLP and threading... Flawed ?
    ... > effects) that are defined separately in the standard. ... Reasoning: ... There's no way to discuss this with respect to threading since the C++ ... POSIX compliance defines additional requirements that make C ...
    (comp.lang.cpp)
  • Re: Removing from a List in Place
    ... bayerj wrote: ... someone tell me the reasoning behind it? ... You are removing the third item, ... This is incorrect. ...
    (comp.lang.python)
  • Re: Removing from a List in Place
    ... > someone tell me the reasoning behind it? ... You are removing the third item, ... list shrinks by 1 and iteration stops. ... Tim Williams ...
    (comp.lang.python)