(no commit message)

diff --git a/ConfiguringRHEL.mdwn b/ConfiguringRHEL.mdwn
index 5dc1b9a..96c5f30 100644 (file)
--- a/ConfiguringRHEL.mdwn
+++ b/ConfiguringRHEL.mdwn
@@ -182,9 +182,11 @@ To load the moonshot extensions, under the root node in /etc/shibboleth/shibbole
 
 
 Further down the same file, find this line:
+
     <AttributeExtractor type="XML" validate="true" path="attribute-map.xml"/>
 
 Directly underneath it, add:
+
     <AttributeExtractor type="GSSAPI" validate="true" path="attribute-map.xml"/>
 
 Note that this file is sensitive to the order of statements.
@@ -204,7 +206,7 @@ This file tells moonshot what encryption options are valid for use with GSS.
 
 ##Testing Functionality
 
-As mentioned earlier, we will be using the Kerberos test tools to make sure that things are working.
+As mentioned earlier, we will be using the Kerberos test tools to make sure that things are working.<br />
 To start the gss-server, run:
     /opt/moonshot/sbin/gss-server host@localhost &
 
@@ -212,7 +214,7 @@ There are two ways to start gss-client – the first specifies an encryption met
     /opt/moonshot/bin/gss-client -mech "{1 3 6 1 4 1 5322 22 1 18}" 127.0.0.1 host@localhost bar
 
 
-The second uses Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO)
+The second uses Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO)<br />
 This chooses the "best" mutually-agreeable encryption method for between client and server.  To invoke the client using SPNEGO, use:
     /opt/moonshot/bin/gss-client -spnego 127.0.0.1 host@localhost bar
 
@@ -244,8 +246,8 @@ This chooses the "best" mutually-agreeable encryption method for between client
     Signature verified.
     NOOP token
 
-Running gss- client produces a massive amount of output.
-The important part is at the end – you should see output similar to what is on the previous slide.
+Running _gss- client produces_ a massive amount of output.<br />
+The important part is at the end – you should see output similar to what is on the previous slide.<br />
 If you do not see the line:
     Attribute local-login-user Authenticated Complete
 Then attribute mapping is not functioning properly, and you need to check your shibboleth configuration.
@@ -256,42 +258,44 @@ To install moonshot-enabled SSH:
     yum install openssh-moonshot-clients openssh-moonshot-server
 
 
-Inside /etc/ssh/sshd_config, and if these values are not set already:
-
-Uncomment UsePrivilegeSeparation and set it to ‘no’
+Inside _/etc/ssh/sshd\_config_, and if these values are not set already:<br />
+Uncomment __UsePrivilegeSeparation__ and set it to __‘no’__
 
        UsePriviligeSeparation no
 
-Uncomment GSSAPIAuthentication and set it to ‘yes’
+Uncomment __GSSAPIAuthentication__ and set it to __‘yes’__
 
        GSSAPIAuthentication yes
 
-Uncomment GSSAPIKeyExchange and set it to ‘yes’
+Uncomment __GSSAPIKeyExchange__ and set it to __‘yes’__
 
        GSSAPIKeyExchange yes
 
-Inside /etc/ssh/ssh_config and if these values are not set already:
-
-Uncomment GSSAPIAuthentication and set it to ‘yes’
+Inside _/etc/ssh/ssh\_config_ and if these values are not set already:<br />
+Uncomment __GSSAPIAuthentication__ and set it to __‘yes’__
 
        GSSAPIAuthentication yes
 
-Uncomment GSSAPIKeyExchange and set it to ‘yes’
+Uncomment __GSSAPIKeyExchange__ and set it to __‘yes’__
 
        GSSAPIKeyExchange yes
 
 ###Running SSH
 
 Finally, we need to start sshd on a seperate port:
-    /opt/moonshot/sbin/sshd –p 2222
 
-At this time we do not recommend running openssh-moonshot as the systemwide SSH client or server – it should be installed alongside the the standard SSH client and server.
-Also note, that sshd must be invoked with its full path, i.e. /opt/moonshot/sbin/sshd.
+    /opt/moonshot/sbin/sshd –p 2222
 
+At this time we do not recommend running __openssh-moonshot__ as the systemwide SSH client or server – it should be installed alongside the the standard SSH client and server.<br />
+Also note, that sshd must be invoked with its full path, i.e. _/opt/moonshot/sbin/sshd._
 
 Finally, try connecting with the following:
+
     /opt/moonshot/bin/ssh –p 2222 –l "" 127.0.0.1
 
-With any luck, magic happens and you are logged in as the user specified in your Chargeable-User-Identity!
-After successfully logging in, don’t forget to type "exit" to end the SSH session and return to the root shell.
-Note in the SSH client command, the option -l "" – this signifies that no username is to be sent to the SSH server. 
+With any luck, magic happens and you are logged in as the user specified in your _Chargeable-User-Identity_!<br />
+After successfully logging in, don’t forget to type __exit__ to end the SSH session and return to the root shell.<br />
+Note in the SSH client command, the option __-l ""__ – this signifies that no username is to be sent to the SSH server. 
+
+##Remote IdP
+This is left for an exercise for the user - at this stage it should just be a case of changing _/etc/radsec.conf_ to point at the right RADIUSd