Change History (11)
comment:1 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 15 years ago
comment:3 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
No. Please, go ahead and do it.
comment:4 by , 15 years ago
| Milestone: | future → 6.4 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:5 by , 15 years ago
When I initially saw this ticket, I didn't read it very well as I know that I had thought about this issue and would address it.
Howewer, DJ's /etc/pam.d/default title to this bug confuses me. This is not what I had in mind. In fact, the only thing I was considering "including" was a system-auth file as the auth service is the only one with multiple entries that would be worth creating a "default" (I prefer system-{service-name}) for
DJ, would you mind giving a bit more input on this as you opened the ticket? Your title and description is way too vague to be of any help.
comment:6 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
comment:8 by , 14 years ago
| Description: | modified (diff) |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
| Summary: | /etc/pam.d/default → /etc/pam.d/system-* |
comment:9 by , 14 years ago
Yes. In an installation that includes only packages in BLFS, system-auth is the only one that makes sense. Going further to include heimdal, ldap, etc... the others certainly do make the job a lot easier.
comment:10 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Created system-{account,auth,password,login} files. Fixed in r8607.
I was already going to do this when I updated the PAM/Shadow packages, but whatever. Are you going to wait until I do those updates?