From 0e078671bbcaafa2ab3aef6a1c1875b3d5607373 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmF293QIINb35puIE44kcDsoUHIhUGyq84" Date: Wed, 9 Nov 2011 10:26:36 -0500 Subject: [PATCH] --- ConfiguringRHEL.mdwn | 38 -------------------------------------- 1 file changed, 38 deletions(-) diff --git a/ConfiguringRHEL.mdwn b/ConfiguringRHEL.mdwn index 30acacc..5b66aa4 100644 --- a/ConfiguringRHEL.mdwn +++ b/ConfiguringRHEL.mdwn @@ -21,43 +21,6 @@ After, either restart your shell session, or: This is required as moonshot currently stores its modified libraries separately to the main system ones to avoid conflicts. This should not be necessary in the future. - -### SELinux set to permissive -Moonshot has a couple of outstanding issues regarding proper labeling of _SELinux_ contexts, causing it to fail when _SELinux_ is enforcing. This should be resolved soon - change the setting in _/etc/sysconfig/selinux_, or in _/etc/rc.local_: - - echo 0 > /selinux/enforce - -### EPEL -Moonshot needs __EPEL__ for a few extra libraries (as pulling them from a semi-supported repository is preferable to repackaging).
-The simplest way to install EPEL is: - - yum install epel-release - -## Moonshot Packages -The RPM's and SRPM's for moonshot are currently hosted at [http://yum.dev.ja.net] - this may change (and in fact, is quite likely to change) in the future. The packages are currently unsigned. - - - -First we need to install and configure moonshot, its dependencies, and a local RADIUS server for testing -In a real deployment, a local RADIUS server is not needed, however it simplifies testing if one is available -__gss-server__ and __gss-client__ are standard Kerberos diagnostic tools, which give us a lot of information that is helpful for debugging -Again, in a real deployment these are not required, but help with testing - -This guide walks through deploying the client, IdP and SP portions of moonshot - depending on your target, some steps may be inappropriate. - -## Environment -### LD_LIBRARY_PATH -__LD_LIBRARY_PATH__ has to have _/opt/moonshot/lib64/_ and _/usr/lib64/freeradius_ added to it.
-The best way to do this is create a file at _/etc/profile.d/moonshot.sh_, with the following: - - if [ [ $LD_LIBRARY_PATH != */opt/moonshot/lib64/:/usr/lib64/freeradius/* ] ] - then - export LD_LIBRARY_PATH=/opt/moonshot/lib64/:/usr/lib64/freeradius/:$LD_LIBRARY_PATH - fi - -This is required as moonshot currently stores its modified libraries separately to the main system ones to avoid conflicts. This should not be necessary in the future. - - ### SELinux set to permissive Moonshot has a couple of outstanding issues regarding proper labeling of _SELinux_ contexts, causing it to fail when _SELinux_ is enforcing. This should be resolved soon - change the setting in _/etc/sysconfig/selinux_, or in _/etc/rc.local_: @@ -86,7 +49,6 @@ To install the diagnostic tools (only needed for testing) and the RADIUSd: yum install freeradius krb5-moonshot-devel moonshot-gss-eap - Once FreeRADIUS is installed, a source of identity needs to be enabled - either the roaming network in the case of an ORPS, or AD/LDAP/etc for an IdP. For now, we'll just use a flat file. Open _/etc/raddb/users_ and locate the following fragment: -- 2.1.4