Petter Reinholdtsen a écrit, le 24/03/2012 22:25:
[Samuel Krempp]If it is too much of hassle to support space characters within passwords, that should be emphasized in the manual (and in the GOsa² interface too).Can you update <URL: http://wiki.debian.org/DebianEdu/Documentation/Squeeze> with some text you would have found useful?
sure, I'll add a warning against using spaces in passwords.I'll try to experiment and see what's happening exactly : does the space results in only the first 'word' being used as password, for everything ? Or maybe the whole password is being used for gosa and truncated when passed to kerberos. Is the whole processing done by regular GOsa, or is there some skolelinux-specific script along the way that could be the culprit ?
If GOsa does indeed mishandle spaces, it should definitely warn against it in the password change interface - and implement checks to make it impossible for someone to define such a password unknowingly. A word of warning in the middle of the user management manual could easily be overlooked.
On a related note, I noticed (the hard way) that entering an IP like 10.0.16.08 instead of 10.0.16.8 in GOsa² will prevent that workstation from connecting (IIRC, the workstation did not authenticate any user from ldap). So another warning about unnecessary zeros in IP might be a good idea.Sound like a bug in gosa. Can you report a bug and update the wiki with the information you would have liked to find in it?
I'm not sure the bug is in GOsa, maybe it's further down in the processing chain. One thing is certain : DNS was working as intended, and "ping host08" did reach said host with IP entered as 10.0.16.08 Is it possible that Skolelinux does some flaky parsing of the IPs stored in LDAP, causing the issue, or can we be sure the bug is GOsa's ?