Avoiding /etc/passwd and /etc/group scans

Christopher Faylor cgf@redhat.com
Tue Oct 22 16:52:00 GMT 2002

On Wed, Oct 23, 2002 at 07:42:35AM +1000, Robert Collins wrote:
>On Wed, 2002-10-23 at 07:40, Christopher Faylor wrote:
>> On Wed, Oct 23, 2002 at 07:36:08AM +1000, Robert Collins wrote:
>> >If we can depend on a correct /etc/passwd we should be able to do
>> >something. We will need to have a postinstall script for cygwin1.dll
>> >that sets the permissions on cygwin1.dll, mkpasswd and mkpgroup, and
>> >ensure that that script runs first, but that is all (off the top of my
>> >head - may be wrong :})
>> Sounds like a catch-22 to me.  How can we run anything except a .bat file
>> invoking windows utilities if cygwin1.dll or any other executable may not
>> actually be executable?
>Yep. Thus the .bat file to ensure that the mkpasswd and mkgroup commands
>and cygwin1.dll are executable.

One of us is missing something.  *How* would you ensure that mkpasswd and
mkgroup are executable?  What executable would you run?


More information about the Cygwin-developers mailing list