<snip> > +# user+group checking > +AC_ARG_ENABLE(usercheck, > + [AC_HELP_STRING([--disable-usercheck], [build TrouSerS without > checking and setting of user/group tss [default=on] (Caution: This is > intended for development purposes only.)])], > + [AS_IF([test "x$enableval" = "xno"], [CFLAGS="$CFLAGS > -DNOUSERCHECK" > + AC_MSG_RESULT([*** Disabling user checking at user request > ***])])],) > +AM_CONDITIONAL(NOUSERCHECK, [test "x$enable_usercheck" = "xno"])
Looks like a sane idea. I do think that in addition to a message at compile time we should add one at runtime. I'd hate for somebody to forget they compiled one way in development and then forgot to change it when they went into production and have the reduced security. A runtime warning would probably help with that. Otherwise the rest of it looks fine. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ TrouSerS-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-tech
