As far as I can tell, the problem which this bug relates to is because
pam_mkhomedir relies on the C mkdir function:
mkdir(dest,0700)
The *desired* operation is to behave as if "/bin/mkdir -p dest" had been
used - nested home directories are neater in many scenarios, and needing
to create most of the directories by hand removes much of the point of
pam_mkhomedir.so
So. There are two options that I can see.
1) Don't use C mkdir, use /bin/mkdir instead. This places a dependancy
on an external executable - but isn't it safe to assume this is always
available on a Debian system?
2) Tokenize the destination, and run C mkdir, piece by piece. This is
the most 'self-contained' solution.
It is of course possible that some users do not WANT recursive behaviour
- for example, if /home is missing (due to a mount problem), they don't
want it created. This ought to be an option for the module though - with
the current behaviour as the default.
I'm not much of a C programmer, but I can try and throw together a patch
if it helps.
--Jo Shields
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
