DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35742>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35742
Summary: segfaults with bogus userdirs
Product: Apache httpd-2.0
Version: 2.0.54
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_userdir
AssignedTo: bugs@httpd.apache.org
ReportedBy: apache@ser1.net
In short, httpd processes handling "~foo" (userdir) requests segfault if the
user is invalid. The log message on the server is:
[notice] child pid 1956 exit signal Segmentation fault (11)
On the client, one gets a connection broken error.
I first noticed this when trying to add a purely LDAP user -- IE,
no /etc/passwd entry. That addition worked fine; I could log in with ssh, get
useful results from getent, su to the user, etc; but hitting
http://myserver.com/~user caused the aforementioned segfault. Adding the user
to /etc/passwd fixed the problem; out of curiosity, I tried accessing
"http://myserver.com/~foo" (where "foo" is in neither /etc/password nor LDAP)
and got the same segfault -- so I don't think it has to do with LDAP in
particular, but rather that mod_userdir can't resolve the user directory. I
would expect an error, but a segfault doesn't seem like appropriate behavior.
As an aside, even if this is fixed, I wonder why mod_userdir can't locate
directories for LDAP-only users. Does mod_userdir go to /etc/passwd directly,
rather than using getent or other NSS API?
--- SER
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
|