From: Timothy <timothy@diyab.net>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Non-PAM Policycoreutils
Date: Thu, 13 Oct 2005 15:56:13 -0400 [thread overview]
Message-ID: <434EBBDD.6040503@diyab.net> (raw)
In-Reply-To: <1129232343.13490.35.camel@moss-spartans.epoch.ncsc.mil>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Stephen Smalley wrote:
> On Thu, 2005-10-13 at 15:18 -0400, Timothy wrote:
>
>>Fixed and tested against CVS. New patch attached.
>
>
> Thanks. Why do you need to define __USE_XOPEN? And should that always
> be done or just in the non-PAM case, i.e. CFLAGS+=-D__USE_XOPEN in the
> else clause of the Makefiles?
>
The crypt defined in unistd.h is only read if __USE_XOPEN is defined so
it's required or make will fail for non-pam builds because the function
authenticate_via_shadow_passwd uses crypt. I tried to add that define
to the CFLAGS in the makefile but it does not see that it is defined for
some reason and still errors out.
Timothy,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFDTrvdSYq2KfPEK/gRA6YCAJ9lpOdS7vXxcSmLUefj0rw23ii9+gCePSfA
NKVY75SH5vCRdPQBoGRUP30=
=Y+Gp
-----END PGP SIGNATURE-----
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2005-10-13 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 18:00 Non-PAM Policycoreutils Timothy
2005-10-13 18:16 ` Stephen Smalley
2005-10-13 19:18 ` Timothy
2005-10-13 19:39 ` Stephen Smalley
2005-10-13 19:56 ` Timothy [this message]
2005-10-13 20:02 ` Stephen Smalley
2005-10-13 22:11 ` Timothy
2005-10-14 15:20 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=434EBBDD.6040503@diyab.net \
--to=timothy@diyab.net \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.