Avoiding /etc/passwd and /etc/group scans

Pierre A. Humblet Pierre.Humblet@ieee.org
Tue Oct 22 11:59:00 GMT 2002

Christopher Faylor wrote:
> I'll provide you with ssh access to sources.redhat.com if you want to
> accumulate your patches on a branch and maybe even offer your own
> "snapshots".

OK. So this branch would have the evolving ntsec stuff, but will be 
populated with stable fork/mmap/tty/etc.. code.
> I really didn't anticipate the level of difficulties that are showing up
> in the cygwin mailing list wrt ntsec, so I'd like to get them solved.
> I'm thinking that if we can get some stuff tested before Corinna returns
> then maybe it will make her job a little easier.

Right, I am sure she will have enough things to do. To really test it 
we need to have people use it. Thus I like the idea of having it in
> Barring that, if you could offer some assurance, on the cygwin mailing
> list, that you're looking into the bugs, that would be helpful.  Then,
> at least, people will realize that their complaints aren't falling on
> deaf ears.

OK. But whatever changes I make can only mask the underlying problem 
with the incorrect passwd file. 

I am not sure where the incomplete passwd files are coming from. 
Old users may have files without sids. 

I just looked at passwd-grp.sh.done (July 28) on my system and noticed 
that the -l switch is not given to mkpasswd/group for domain users. 
So they may have problems when they login as a local user.
Similarly software installed as a local user won't work if the
user logs in later as a domain user.

Is there any harm in always giving the -l and -d switches? 
In other words, what happens with -d on a standalone machine?
That won't solve everything but it is simple and better than what 
is in my passwd-grp.sh.done


More information about the Cygwin-developers mailing list