1 First we need to install and configure moonshot, its dependencies, and a local RADIUS server for testing<br />
2 In a real deployment, a local RADIUS server is not needed, however it simplifies testing if one is available<br />
3 __gss-server__ and __gss-client__ are standard Kerberos diagnostic tools, which give us a lot of information that is helpful for debugging<br />
4 Again, in a real deployment these are not required, but help with testing
6 This guide walks through deploying the client, IdP and SP portions of moonshot - depending on your target, some steps may be inappropriate.
10 __LD_LIBRARY_PATH__ has to have _/opt/moonshot/lib64/_ and _/usr/lib64/freeradius_ added to it.<br />
11 The best way to do this is create a file at _/etc/profile.d/moonshot.sh_, with the following:
13 if \[[ $LD_LIBRARY_PATH != */opt/moonshot/lib64/:/usr/lib64/freeradius/* ]]
15 export LD_LIBRARY_PATH=/opt/moonshot/lib64/:/usr/lib64/freeradius/:$LD_LIBRARY_PATH
18 After, either restart your shell session, or:
20 source /etc/profile.d/moonshot.sh
22 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.
24 ### SELinux set to permissive
25 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_:
27 echo 0 > /selinux/enforce
30 Moonshot needs __EPEL__ for a few extra libraries (as pulling them from a semi-supported repository is preferable to repackaging).<br />
31 The simplest way to install EPEL is:
33 rpm -ivh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm
34 yum install epel-release
37 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.<br />
38 Example _/etc/yum.repos.d/moonshot.repo_
42 baseurl=http://yum.dev.ja.net/RPMS/x86_64/
45 After setting up the repository definition, we'll set up a composite ORPS/IdP.
48 To install the diagnostic tools (only needed for testing) and the RADIUSd:
50 yum install freeradius krb5-moonshot-devel moonshot-gss-eap
52 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:
55 # This is a complete entry for "steve". Note that there is no Fall-Through
56 # entry so that no DEFAULT entry will be used, and the user will NOT
57 # get any attributes in addition to the ones listed here.
59 # steve Cleartext-Password := "testing"
60 # Service-Type = Framed-User,
61 # Framed-Protocol = PPP,
63 Uncomment the line beginning __steve__.
65 __Chargeable-User-Identity__ is the value used to decide what user account to log in the user as on the SSH server.<br />
66 This value would normally be set by your local RADIUS proxy (ORPS) – so in a real deployment, rather than statically logging the user in as __moonshot__ you may decide to use something like __steve-camford.ac.uk__.<br />
67 If anonymity is required, you could use a Perl or Python script to generate something like __user-789-camford.ac.uk__.<br />
68 The exact value does not matter – only that the mappings are consistent, so that the user gets access to the same local account each time.
69 To allow creation of accounts on demand you could use __LDAP__ – when the ORPS sees a successful authentication, it could trigger a script that creates the desired account in an __LDAP__ domain.
70 It is not guaranteed that __Chargeable-User-Identity__ will be used permanently – in the future a specific RADIUS attribute may be created instead.
72 To activate CUI insertion, Edit _/etc/raddb/sites-enabled/default_, and find the post-auth section, and add the following:
75 Chargeable-User-Identity = "moonshot"
78 Note in the case of an ORPS you need to unfilter this attribute in _/etc/raddb/attrs_ to prevent this attribute from being stripped on roaming requests.
80 A legacy attribute required for SSH at this time is the user name returned by the IdP. To make this happen, Edit _/etc/raddb/sites-enabled/inner-tunnel_, find the following and uncomment it:
83 # User-Name = "%{request:User-Name}"
86 Finally, set the EAP type in use by moonshot (EAP-TTLS) by editing _/etc/raddb/eap.conf_
88 default_eap_type = md5
90 FreeRADIUS now has a very minimal IdP/ORPS configuration, and can be started with:
92 service radiusd restart
94 If you encounter any issues, you can run radius in debug mode to see what is going on internally.
99 When in debug mode, FreeRADIUS acts as an interactive program, so it should be run on a separate console, or under GNU Screen.
102 First we need a minimal _/etc/radsec.conf_
104 dictionary = "/etc/raddb/dictionary"
111 hostname = "127.0.0.1"
113 secret = "testing123"
117 This tells the moonshot SP where to find a RADIUS server for authentication - in this case, we will use the local server just configured.<br />
118 Moonshot will ultimately use RADSEC for communicating with the radius server – in which case you would use __transport="TCP"__ in _/etc/radsc.conf_<br />
119 Ultimately, the final values depend on the deployment – probably the address, port and secret used by your ORPS.
123 Next, a file is created in the home directory at _~/.gss\_eap\_id_ – this is the file that moonshot looks in for credentials.
124 The format is very simple – username followed by a password. For now, set it to:
129 In a deployment with a GUI, this file is replaced by the Moonshot Identity Selector. It is conceivable in the future that the Identity Selector GUI will be supplemented with a curses-like UI, or other mechanism allowing console usage.
133 Moonshot uses _libshib_ to parse RADIUS and SAML attributes – SAML assertions can be embedded inside RADIUS responses by the IdP, allowing an ORPS to exercise a very fine-grained authorization policy.
134 In the demo we just use a very simple example – mapping the _Chargeable-User-Identity_ to a local user account, but in a real deployment you could map a SAML attribute to the user account just as easily.
136 Delete _/etc/shibboleth/attribute-map.xml_ and replace it with:
138 <Attributes xmlns="urn:mace:shibboleth:2.0:attribute-map" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
139 <GSSAPIAttribute name="urn:ietf:params:gss-eap:radius-avp urn:x-radius:89" id="local-login-user"/>
142 In this case, 89 corresponds to _Chargeable-User-Identity_, which is mapped to _local-login-user_, which sets the local account that the user will be given access to.
144 To load the moonshot extensions, under the root node in _/etc/shibboleth/shibboleth2.xml_, add:
146 <Library path="plugins.so" fatal="true"/>
149 Further down the same file, find this line:
151 <AttributeExtractor type="XML" validate="true" path="attribute-map.xml"/>
153 Directly underneath it, add:
155 <AttributeExtractor type="GSSAPI" validate="true" path="attribute-map.xml"/>
157 Note that this file is sensitive to the order of statements.
161 This file tells moonshot what encryption options are valid for use with GSS.
164 # Sample mechanism glue configuration for EAP GSS mechanism.
166 # Any encryption type supported by Kerberos can be defined as the
167 # last element of the OID arc.
169 eap-aes128 1.3.6.1.4.1.5322.22.1.17 mech_eap.so
170 eap-aes256 1.3.6.1.4.1.5322.22.1.18 mech_eap.so
172 ##Testing Functionality
174 As mentioned earlier, we will be using the Kerberos test tools to make sure that things are working.<br />
175 To start the _gss-server_, run:
176 /opt/moonshot/sbin/gss-server host@localhost &
178 There are two ways to start _gss-client_ – the first specifies an encryption method to use by its OID 1.3.6.1.4.1.5322.22.1.18 (as seen in /etc/gss/mech):
179 /opt/moonshot/bin/gss-client -mech "{1 3 6 1 4 1 5322 22 1 18}" 127.0.0.1 host@localhost bar
182 The second uses __Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO)__<br />
183 This chooses the "best" mutually-agreeable encryption method for between client and server. To invoke the client using __SPNEGO__, use:
184 /opt/moonshot/bin/gss-client -spnego 127.0.0.1 host@localhost bar
188 Attribute local-login-user Authenticated Complete
195 Accepted connection: "steve"
196 Sending init_sec_context token (size=150)...continue needed...
198 context flag: GSS_C_MUTUAL_FLAG
199 context flag: GSS_C_REPLAY_FLAG
200 context flag: GSS_C_SEQUENCE_FLAG
201 context flag: GSS_C_CONF_FLAG
202 context flag: GSS_C_INTEG_FLAG
203 "steve" to "host/moonbuildcentos.dev.ja.net", lifetime -1, flags 13e, locally initiated, open
204 Name type of source name is { 1 2 840 113554 1 2 1 1 }.
205 Mechanism { 1 3 6 1 5 5 2 } supports 4 names
206 0: { 1 2 840 113554 1 2 1 1 }
207 1: { 1 2 840 113554 1 2 1 2 }
208 2: { 1 2 840 113554 1 2 1 3 }
209 3: { 1 2 840 113554 1 2 1 4 }
210 Received message: "testing"
214 Running _gss-client_ produces a massive amount of output.<br />
215 The important part is at the end – you should see output similar to what is on the previous slide.<br />
216 If you do not see the line:
217 Attribute local-login-user Authenticated Complete
218 Then attribute mapping is not functioning properly, and you need to check your shibboleth configuration.
221 To install moonshot-enabled SSH:
223 yum install openssh-moonshot-clients openssh-moonshot-server
226 Inside _/etc/ssh/sshd\_config_, and if these values are not set already:<br />
227 Uncomment __UsePrivilegeSeparation__ and set it to __‘no’__
229 UsePriviligeSeparation no
231 Uncomment __GSSAPIAuthentication__ and set it to __‘yes’__
233 GSSAPIAuthentication yes
235 Uncomment __GSSAPIKeyExchange__ and set it to __‘yes’__
237 GSSAPIKeyExchange yes
239 Inside _/etc/ssh/ssh\_config_ and if these values are not set already:<br />
240 Uncomment __GSSAPIAuthentication__ and set it to __‘yes’__
242 GSSAPIAuthentication yes
244 Uncomment __GSSAPIKeyExchange__ and set it to __‘yes’__
246 GSSAPIKeyExchange yes
250 Finally, we need to start sshd on a seperate port:
252 /opt/moonshot/sbin/sshd –p 2222
254 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 />
255 Also note, that sshd must be invoked with its full path, i.e. _/opt/moonshot/sbin/sshd._
257 Finally, try connecting with the following:
259 /opt/moonshot/bin/ssh –p 2222 –l "" 127.0.0.1
261 With any luck, magic happens and you are logged in as the user specified in your _Chargeable-User-Identity_!<br />
262 After successfully logging in, don’t forget to type __exit__ to end the SSH session and return to the root shell.<br />
263 Note in the SSH client command, the option __-l ""__ – this signifies that no username is to be sent to the SSH server.
266 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