search for: selinux_msg

...,19 +3155,18 @@ LIBSELINUX="" > AC_ARG_WITH(selinux, > [ --with-selinux Enable SELinux support], > [ if test "x$withval" != "xno" ; then > + save_LIBS="$LIBS" > AC_DEFINE(WITH_SELINUX,1,[Define if you want SELinux support.]) > SELINUX_MSG="yes" > AC_CHECK_HEADER([selinux/selinux.h], , > AC_MSG_ERROR(SELinux support requires selinux.h header)) > AC_CHECK_LIB(selinux, setexeccon, [ LIBSELINUX="-lselinux" ], > AC_MSG_ERROR(SELinux support requires libselinux library)) > - save_LIB...

Hi If I try to run configure for openssh-5.1p1 with --wtih-selinux option it fails giving the error "selinux support requires selinux library" all of the below also dont work a) --wtih-selinux b) --wtih-selinux=path of cross complied library c) LDFLAGS=-Lpath of cross complied library if I remove --wtih-selinux option I am able to everything is fine. How to solve this error? Thanks

...openssh-3.9p1_selinux/configure.ac --- openssh-3.9p1_vanilla/configure.ac 2004-08-16 15:12:06.000000000 +0200 +++ openssh-3.9p1_selinux/configure.ac 2004-09-07 17:41:15.000000000 +0200 @@ -2218,6 +2218,18 @@ [#include <arpa/nameser.h>]) ]) +# Check whether user wants SELinux support +SELINUX_MSG="no" +AC_ARG_WITH(selinux, + [ --with-selinux Enable SELinux support], + [ if test "x$withval" != "xno" ; then + AC_DEFINE(WITH_SELINUX) + SELINUX_MSG="yes" + AC_CHECK_HEADERS(selinux.h) + LIBS="$LIBS -lselinux" + fi + ]) + # Check whether u...

...(LIBPAM) fi ] ) @@ -3157,19 +3155,18 @@ LIBSELINUX="" AC_ARG_WITH(selinux, [ --with-selinux Enable SELinux support], [ if test "x$withval" != "xno" ; then + save_LIBS="$LIBS" AC_DEFINE(WITH_SELINUX,1,[Define if you want SELinux support.]) SELINUX_MSG="yes" AC_CHECK_HEADER([selinux/selinux.h], , AC_MSG_ERROR(SELinux support requires selinux.h header)) AC_CHECK_LIB(selinux, setexeccon, [ LIBSELINUX="-lselinux" ], AC_MSG_ERROR(SELinux support requires libselinux library)) - save_LIBS="$LIBS" - LI...

I've been trying to figure out why I can't seem to use SSHFP fingerprints delivered via DNSSEC, which led me to try to figure out why OpenSSH won't use DNSSEC on my NetBSD-4-branch platform. It turns out that around line 70 in openbsd-compat/getrrsetbyname.c, we have the following: /* to avoid conflicts where a platform already has _res */ #ifdef _res # undef _res

Dear developers, as reported earlier, recent versions of OpenSSH (4.3p1, 4.3p2 as well as the current CVS) on IRIX 5.3 exhibit a DNS resolution failure. Even for perfectly valid hostnames they return "no address associated with name". After some digging through the code I found what is causing this strange behaviour. Basically it was introduced with the following change:

...ho " PAM support: $PAM_MSG" +echo " SCTP support: $SCTP_MSG" echo " OSF SIA support: $SIA_MSG" echo " KerberosV support: $KRB5_MSG" echo " SELinux support: $SELINUX_MSG" diff --git a/misc.c b/misc.c index e4c8c32..843ccd4 100644 --- a/misc.c +++ b/misc.c @@ -42,6 +42,9 @@ #include <netinet/in_systm.h> #include <netinet/ip.h> #include <netinet/tcp.h> +#ifdef USE_SCTP +# include <netinet/sctp.h> +#endif #include <ctype.h> #i...

Hi, The main (and probably the only) use case of this PAM module is to let sudo authenticate users via their ssh-agent, therefore without having to type any password and without being tempted to use the NOPASSWD sudo option for such convenience. The principle is originally implemented by an existing module [0][1] and many pages that explain how to use it for such purpose can be found online.