Subject: Re: need for end*ent()?
To: Hubert Feyrer <>
From: John Nemeth <>
List: tech-security
Date: 09/14/2005 00:07:47
On Dec 30,  7:52pm, Hubert Feyrer wrote:
} On Tue, 13 Sep 2005, John Nemeth wrote:
} >     I am working on libwrap to remove a reference to getgrnam().
} > Immediately after the use of getgrnam(), it calls endgrent() (there is
} > also a call to endpwent()).  I'm considering removing these in order to
} > reduce possible side effects on applications using the library.
} > However, I'm wondering if they should be left to ensure database
} > updates are seen in long running daemons as per this paragraph in the
} > manpage:
} >
} >     It is dangerous for long-running programs to keep the file descriptors
} >     open as the database will become out of date if it is updated while the
} >     program is running.
} >
} > Does anybody else have any thoughts on this issue?
} The calls exist and are being used (properly) for the stated reason.
} Why would you want to remove them?

     Because if the application happens to iterating a database by
using getgrent() or getpwent() at the time it makes a call to libwrap I
wouldn't want its pointer to be reset.  I have no idea why an
application would do this.  However, I don't think it is up to me or
necessarily up to any particular library to make this choice for it.

}-- End of excerpt from Hubert Feyrer