Equipment/Turing: Difference between revisions

Equipment/Turing (view source)

36 bytes removed , 23 November 2018

m

Updated LDAP info (no more Denning as it goes to ldap-secondary now, and it does work)

1,034

edits

@@ Line 32: / Line 32: @@
 == LDAP ==
-Turing has an LDAP db on it that is replicated to [[denning]] for use on machines in the space.
+Turing has an [[LDAP]] db on it that is replicated to ldap-secondary (Hackspace VM in Wembley) for use on machines in the space.
-It sort of works.
+Turing has iptables rules that allow access to the [[LDAP]] server from ldap-secondary (Hackspace VM).
-Turing has iptables rules that allow access to the LDAP server from denning.
+We use a schema that is compatible with Samba for 2 reason:
-The LDAP server uses an ssl cert from startcom, it expires on Mar 25 2015.
+* We might want user logins to Samba at some point
+* The sambaNTPassword attribute is understood by FreeRADIUS and is needed for MS-CHAP auth for spacefed.
-We use a schema that is compatible with samba for 2 reason:
-* We might want user logins to samba at some point
-* The sambaNTPassword attribute is understood by freeradius and is needed for MS-CHAP auth for spacefed.
 however the sambaNTPassword hash is quite weak, and the sambaLMPassword hash is silly, so ideally:
@@ Line 91: / Line 87: @@
 * might need to add an index to memberUid
-=== Changes to tools on turing ===
+=== Changes to tools on Turing ===
 The smbldap tools were patched with these patches