On Tue, 3 Aug 2004, Andrew Stribblehill wrote: > I'm trying to improve httpd's mod_userdir so that it knows it > shouldn't serve ~fool when user 'fool' has an administratively > prohibited shell, so: > > UserDir DisableShell /bin/badlad > > To this end, I need a function to query the user's shell. It seems > sensible to me (though I am new to apr) that it should go into apr.
The problem is that there's no portable concept of a shell, right? I mean, users on Windows all get the same shell (or at least there's no shell associated with their uid as such), and certainly this wouldn't apply to netware... how would those platforms be handled, besides returning APR_ENOTIMPL? I don't think they can be. Typically our policy in APR has been that we provide the lowest common denominator of functionality... if a concept doesn't map onto anything but unix, we would tend to be hesitant to make it part of APR. That's not to say there are no non-portable things in APR, but they're all stuffed away in apr_os_*... I guess maybe if this were apr_os_shell_get() I'd be more willing to consider it. :)
