| Summary: | Add LDAP support to sshd | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Chris Pepper <pepper> | ||||
| Component: | PAM support | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED WONTFIX | ||||||
| Severity: | enhancement | CC: | buffer.g.overflow, djm, ebourg, mindrot.robmoore, ryanlee, scott | ||||
| Priority: | P2 | ||||||
| Version: | -current | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| URL: | http://code.google.com/p/openssh-lpk/ | ||||||
| Attachments: |
|
||||||
|
Description
Chris Pepper
2007-05-22 04:41:33 AEST
Created attachment 1826 [details] patch adding public key authentication via LDAP patch pulled from http://openssh-lpk.googlecode.com/svn/trunk/patch/contrib/openssh-lpk-0.3.10_5.4p1.patch There seem to be plenty of interest downstream in supporting LDAP as a network datastore for pubkeys (e.g. going back a few years, RH, Debian, and Ubuntu have open bugs tracking this one), so, if this patch isn't acceptable as offered, might it be possible to understand the reasons and see if it's possible to arrive at an acceptable solution ? We won't be integrating LDAP into sshd. There are patches to allow sshd to fetch keys using a helper program (which could in turn use LDAP) that will be considered, but I haven't had time to review them properly. Do you have a pointer to that work? Is there anything someone could do to help progress down that path? close resolved bugs now that openssh-5.9 has been released |