From Mandriva Community Wiki

Contents 1 Interest 2 Creation 2.1 User 2.1.1 Applying 2.1.2 Testing 2.1.2.1 SVN access 2.1.2.2 Cluster access (packagers only) 2.1.2.3 Mail redirection 2.2 Sponsor 2.3 Admin 3 Management 3.1 Password 3.2 Web page 3.3 Mail address 3.4 SSH key

Interest

You need an account on mandriva infrastructure in order to access the following resources:

• subversion with write access
• build cluster
• authentication on maintainer database
• centralized authentication on wiki and bugzilla

An account also implies the following standard unix facilities:

• a mandriva.org mail address
• a web page on kenobi.mandriva.com

Creation

Account creation requires interaction between three people:

• a user
• a sponsor
• an admin

The following describe each people responsability.

User

Applying

1. Create an ssh key, for a more details about this step read here.
2. Open a ticket in Mandriva's Bugzilla. Set these two ticket fields as follows:
   1. Product: Mandriva Build System
   2. Component: Accounts
3. You should include the following information in the bugzilla ticket:
   1. The exact task you're applying for (packaging, translating... etc).
   2. A valid mail address.
4. Attach your public ssh key to the ticket
5. Get a sponsor (a packaging mentor for packaging, a translation coordinator for translating) to approve your request
   1. A good idea to get someone to sponsor you is by sending email introducing yourself asking for sponsorship to cooker mailing list

That's it! good luck.

Testing

SVN access

Install subversion (if you don't already have it)

 urpmi subversion

Try to access any part of subversion through ssh. You will be asked the password for your SSH key.

 svn ls svn+ssh://<login>@svn.mandriva.com/svn/soft/drak3d/trunk/po drak3d

Cluster access (packagers only)

Try to access mandriva SSH gateway

 ssh <login>@kenobi.mandriva.com

For more information about ssh configuration see this page.

Mail redirection

Send a mail to your <login>@mandriva.org address

Sponsor

The account creation request should be approved, with exact privilege required if needed (see task-specific policy for details).

Admin

Once the account creation request has been approved, the account has to be created, meaning:

• an ldap user entry, for cluster/svn access
  • public key import
  • initial mail redirection
• a my.mandriva.com entry, for maintainer db/wiki/bugzilla access

Detailed instructions for cluster admins' tasks can be found at Development/Resources/Cluster/Admin.

Management

Password

Mandriva infrastructures actually use two authentication backends:

• a ldap server, for unix account management (cluster, subversion)
• a mysql server, for web applications account management (wiki, bugzilla, maintainer database)

Only the password for the second one (my.mandriva.com) can be initialized or changed, through my.mandriva.com login page.

Web page

The content of ~/public_html directory is accessible at http://kenobi.mandriva.com/~<login>

Mail address

There is no IMAP/POP server available, so you should redirect any incoming mail to your @mandriva.org address to another address.

To check current redirection:

 ldapsearch -x uid=<login> mailForwardingAddress

To change it (LDAP password needed):

 ldapmodify -x -H ldap://svn.mandriva.com -Z -D uid=<login>,ou=People,dc=mandriva,dc=com -W <<EOF
 > dn: uid=<login>,ou=People,dc=mandriva,dc=com
 > changetype: modify
 > replace: mailForwardingAddress
 > mailForwardingAddress: <address>
 >EOF

SSH key

The authorized public keys are also stored in ldap.

To check current keys (LDAP password needed):

 ldapsearch -x -Z -D uid=<login>,ou=People,dc=mandriva,dc=com -W uid=<login> sshPublicKey:

To change it (LDAP password needed):

 ldapmodify -x -H ldap://svn.mandriva.com -Z -D uid=<login>,ou=People,dc=mandriva,dc=com -W <<EOF
 > dn: uid=<login>,ou=People,dc=mandriva,dc=com
 > changetype: modify
 > replace: sshPublicKey
 > sshPublicKey: <key>
 >EOF

You can also use send-sshkey-ldap.py command on kenobi.

If you don't have an ldap password, ask an admin.