Ed Schouten 7845988449 Don't include <utmp.h> when using <utmpx.h>. ... libopie includes both <utmp.h> and <utmpx.h> in this case and uses some #defines to let the code use struct utmpx and its utility functions. We'd better not include <utmp.h> here, because maybe it will not be present in the future.		2010-01-11 16:27:56 +00:00
..
accessfile.c
atob8.c
btoa8.c
btoe.c
btoh.c
challenge.c	Resolve conflicts.	2002-03-21 23:42:52 +00:00
generator.c	Resolve conflicts.	2002-03-21 23:42:52 +00:00
getsequence.c
getutmpentry.c	Don't include <utmp.h> when using <utmpx.h>.	2010-01-11 16:27:56 +00:00
hash.c	Resolve conflicts.	2002-03-21 23:42:52 +00:00
hashlen.c	Resolve conflicts.	2002-03-21 23:42:52 +00:00
insecure.c	Don't include <utmp.h> when using <utmpx.h>.	2010-01-11 16:27:56 +00:00
keycrunch.c
lock.c	Resolve conflicts.	2002-03-21 23:42:52 +00:00
login.c	Don't include <utmp.h> when using <utmpx.h>.	2010-01-11 16:27:56 +00:00
logwtmp.c
lookup.c
Makefile.in
md4c.c
md5c.c
newseed.c	When computing a new seed for an existing user, opienewseed() would	2003-01-22 10:55:36 +00:00
open.c
parsechallenge.c
passcheck.c
passwd.c
randomchallenge.c
readpass.c
readrec.c	Create /etc/opiekeys with 0600, not 0644	2005-07-29 09:59:24 +00:00
unlock.c
verify.c
version.c
writerec.c	Create /etc/opiekeys with 0600, not 0644	2005-07-29 09:59:24 +00:00