> > >2) I have had a look at the BSD auth implementation proposal which you
> > >   posted in [3].  All BSD auth logic resides in libutil, and there is
> > >   no reason to have pw_dup(3) separated from it in libc; neither does
> > >   pw_dup(3) access any libc internals in which case it being
> > >   implemented in libc would be a sensible choice.  It's also worth
> > >   noting that the bulk of password database utility functions already
> > >   reside in libutil.
> >
> > 	it was a mistake.  all auth*.c has to reside in libc.
> 
> 1) Why?

	based on comment from openbsd folks (who has much more experience
	in BSD auth than me).

> 2) If the reason for having this in libc is BSD Auth, shouldn't this call
> wait?

	i committed it because it is useful by itself.  it has nothing to do
	with BSD auth integration attempt.  (libutil/libc choice was affected
	by question 1, yes)

itojun