Spacenet

NURDs Inventory
Owner	Space
Status	Infrastructure
Hostname	spacenet
Tool	No
Tool category

{{{Name}}}Property "Tool Name" (as page type) with input value "{{{Name}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{{InventoryOwner}}}Property "Tool Owner" (as page type) with input value "{{{InventoryOwner}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Location}}}Property "Tool Location" (as page type) with input value "{{{Location}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

What is it

SpaceFED is an inter-(hacker)space federated authentication platform which currently offers the following services:

• spacenet - federated authentication using RADIUS, useful for 802.1X and more
• spacesaml - federated authentication for cloudservices

We have implemented SpaceNET on the E4200 access point. This means we have an LDAP with users, hashes and other stuff, and a FreeRADIUS server for wireless authentication (802.1x) which uses the fore-mentioned LDAP to authenticate. This all runs on nurdservices.

Also, in the future we can use SpaceSAML to authenticate our webservices (mediawiki, gallery, i dunno) against this database.

Where is it

There are 3 AP's:

• The E4200 in the space
• A US Robotics 5453 AP in the open area on the 1st floor to cover the central hall. Hostname nurds-ap-02.
• A US Robotics 5453 AP in the server room on the 2nd floor. Hostname nurds-ap-01.

How do I use it

New users

You will need to start by logging in to the LDAP from within the network with their new LDAP user account.

The reason for this is that passwords of new accounts are set in the field sambaLMPassword, but spacenet works with the NTPassword field. Changing your password via the FusionDirectory web interface changes both these fields to the same new value. You can also just re-enter your old password.

Linux

To log into SpaceNet (SSID spacenet) follow these steps, except the WPA supplicant settings there are complete bullshit. The correct ones are

network={
        ssid="spacenet"
        key_mgmt=WPA-EAP
        eap=PEAP
        anonymous_identity="anonymous@nurdspace.nl"
        phase2="auth=MSCHAPV2"

        # set correct username, password, and path to cert file:
        identity="username@nurdspace.nl"
        password="yada"
        ca_cert="/etc/wpa_supplicant/spacenet.pem"
}

Certificate file:

-----BEGIN CERTIFICATE-----
MIICxjCCAa4CCQDXE/Qr23LoejANBgkqhkiG9w0BAQUFADAlMSMwIQYDVQQDExpu
dXJkc2VydmljZXMubnVyZHNwYWNlLmxhbjAeFw0xMzAzMjkyMTM3MzNaFw0yMzAz
MjcyMTM3MzNaMCUxIzAhBgNVBAMTGm51cmRzZXJ2aWNlcy5udXJkc3BhY2UubGFu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwPTsBJ5yt+QOKiAV1TJk
VdTKO8DggKG7ba35hjECJ5xyq2G8QUs9VtuWWgBqLKeUPkb0f0PRBcgq4JpN8eKg
v2Yt5hhYCZOtho/bcZr6hOZIcMhkQxfDwmf7PN1VLcszjENLon/frRy804tHFHxS
u2S6/0elIrnKv520anS7Zn5AifS7i4lg04zZsoDujjkLBBW9jDXpl8HRsk6Gp1xA
6BAIf0TjN8hsoLqNYCetM2H5yWva1vmuiytgebdM8OUKpajNH/Z3rr4smI9pTXkB
zr1PVsshpU0ZI204e9KomcvqrReDBR/TW0zf4fhhbPa4+81WkHxSeibidnuBb51j
IwIDAQABMA0GCSqGSIb3DQEBBQUAA4IBAQCuWMrnxjNMARCuGo5A9pkDDMWudchC
i8ZiUVmzCfEoNFhYr6IaSslyJ4NY3AppOOzEKaEuWTkecftNBj0YMvZM5wZUAtlu
SZy8ilefonL9AsGKyWOD3Maq2DhBvv49MT/pN/OF43bhuQCmojdC+y3TcSrIhABe
TJb8Kt6nnH0qNqSDnpWNx+kdxdfYV8ivpFdRa5TT7pw6zXVTrCH2ysXIhPWGroJ8
1Gssprw3HVH6jGHYqCiM7nJnsMimqDICSoNMVLRq8UK+SSoJ74WW1ICvHdsnkG3c
4wRDP3p90oixX2uPSLNpC3MbPIPbpOL7/0nrAAlM7AuqssBEw9a8vHv3
-----END CERTIFICATE-----

Windows

To log into SpaceNet (SSID spacenet) follow these steps.

Maintenance

Todo list

• Check local radius instance
• AP Upgrade