| Summary: | Account request: ovitters | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Olav Vitters <olav> |
| Component: | Account request | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | sysadmin-bugs |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | RSA key 2048 02:56:df:00:ac:27:eb:bf:21:58:3e:f8:73:8d:18:38 | ||
|
Description
Olav Vitters
2011-08-27 21:51:39 CEST
Created attachment 741 [details]
RSA key 2048 02:56:df:00:ac:27:eb:bf:21:58:3e:f8:73:8d:18:38
Checked bug 2446 -- accidentally also added an empty SSH key. Cannot seem to update it, nor delete it.. if someone could remove that. Hello, You should now be able to commit on the svn. For the ssh key, you can add it on https://identity.mageia.org/ : - connect on https://identity.mageia.org/ - add an attribute ( bottom of the form ) of type : sshPublicKey , with the content of the public key A cron job is run on the svn server every 10 minutes to update the ssh keys from ldap. It's also possible to use the password to checkout and commit. To check that everything is working, just use ssh svn.mageia.org, and type the password if needed. This should print a list of groups, and a message about shell access being restricted. Please also note that once having a svn commit access, the password reset feature requires to be acknowledged by a admin. Closing Status:
NEW =>
RESOLVED
Nicolas Vigier
2014-05-08 18:05:35 CEST
CC:
boklm =>
(none) |