| Summary: | sys-auth/pam_radius-1.3.17 (new ebuild) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | RB <aoz.syn> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | droid, net-dialup, pam-bugs+disabled, strogdon |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | ebuild | ||
|
Description
RB
2008-02-22 04:06:10 UTC
Created attachment 144286 [details]
ebuild
*** Bug 33375 has been marked as a duplicate of this bug. *** The ebuld looks good now; I have no use for it nor a way to test, though, so someone has either to proxy-maintain it or find a maintainer for it. CCing net-dialup as all the radius implementations seems to fall into that herd, and they might be interested in it. This ebuild works fine, as it should, on amd64. I need pam_radius to authenticate with a radius server. Is there any way to get this in portage (or somewhere) in such a way that every time I upgrade pam I don't get complaints about the pam_radius stuff in /etc/pam.d? This pluggable module should be easy to maintain. Fixed in cvs. |