Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

OpenSSH is a freely available version of the SSH connectivity tools, and is the standard version of SSH used by many linux distributions. See for more information.


1. Overview

No current version of OpenSSH currently natively supports moonshot, but patches are available for v5.3 and v5.9 of OpenSSH to fix the issues that stop it from working. Ultimately we hope that these patches will become a standard part of OpenSSH, so that OpenSSH will work without any extra work being necessary.

2. Compatibility

2.1. Key

In the tables below, the following icons have the following meanings:

  • (tick) - This version of the software has been tested and verified as supporting Moonshot.
  • (error) - This version of the software has been tested and verified as not supporting Moonshot.
  • (question) - This version of the software has not yet been tested thoroughly and its status is not known. Let us know if you have tried it and whether it worked or not!

2.2. Compatibility List

Note that accessing supported versions of this software requires a Moonshot compatible client - see the next section for details on which clients are supported.

Any versions not listed below list have not yet been tested. If you do so, please let us know!

OS versionCompatible?Packages Available?Notes
CentOS 6(tick)(tick)Using our pre-compiled package. Re-compiling instructions available.
Debian 7(tick)(tick)Using our pre-compiled package.
Debian 8(tick) Building instructions available.
RHEL 6(tick)(tick)Using our pre-compiled package. Re-compiling instructions available.
Scientific Linux 6 (tick)(tick)Using our pre-compiled package. Re-compiling instructions available.
Ubuntu 12.04 LTS(tick)(tick)Using our pre-compiled package for Debian 7

3. Installation & Configuration Instructions

How you set up a Moonshot-enabled version of the OpenSSH server will differ depending on your OS. See the relevant pages for your particular distribution:

4. Client Compatibility

The following clients are known to work with this server software using Moonshot authentication (click on the link to see further information about enabling Moonshot in that client):

5. Next Steps

Once you have installed the software, what happens next?

5.1. Account Mapping

Read our General account mapping advice page before you go any further to get an overview of the general options available for mapping federation provided identities to local accounts.

5.1.1. Mapping to an account specified in a SAML attribute

Moonshot uses Shibboleth libraries to parse RADIUS and SAML attributes - SAML assertions can be embedded inside RADIUS responses by the IdP, allowing an IdP to exercise a very fine-grained authorisation policy. One potential use of this is to allow the Moonshot IdP to specify which account the user should log in to your SSH server as. To do this, it passes across a username in a SAML attribute and your server maps that to a local user account (via local-login-user).

  1. Edit /etc/shibboleth/shibboleth2.xml and insert the following lines if they don't exist (note that this should go directly after the opening <SPConfig ... clockSkew="180"> stanza:

    	<Library path="" fatal="true" />
  2. Edit /etc/shibboleth/attribute-map.xml and find the SAML attribute that the Moonshot IdP will be sending you that contains the username.


    We want to map from the incoming SAML2 representation of "eduPersonEntitlement"

    <Attribute name="urn:oid:" id="entitlement"/>
  3. Change the id of the attribute to "local-login-user".


    We change the attribute defining the SAML2 representation of "eduPersonEntitlement" such that its id becomes "local-login-user"

    <Attribute name="urn:oid:" id="local-login-user"/>
    In the standard Moonshot distribution, SSH will look for local-login-user to determine who to authenticate the user as. This attribute mapping will be managed by the XML assertion in the FreeRADIUS reply for a successful authentication.

5.1.2. Further mapping options

To Come!



  • No labels