#836 closed defect (wontfix)
OpenSSH 3.9p1 w/PAM
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | BOOK | Version: | SVN |
Severity: | minor | Keywords: | |
Cc: |
Description ¶
The BLFS book forgot to mention that if you installed PAM you will need to run configure with "--with-pam" and that you will need to install the sshd.pam file
cp $SRC/contrib/sshd.pam.generic /etc/pam.d (or pam.conf, with modifications)
Change History (4)
comment:1 by , 20 years ago
Milestone: | future → 6.0 |
---|---|
Priority: | high → normal |
Severity: | normal → minor |
Summary: | OpenSSH 3.8.1pl1 w/PAM → OpenSSH 3.9p1 w/PAM |
Version: | CVS → SVN |
comment:2 by , 20 years ago
Some more input on this issue:
I'm working on a recently built system with PAM and OpenSSH. PAM is configured and the sshd daemon is running. The default sshd_config file does not enable PAM. You would have to deliberately change the file to use PAM.
So, that said, and with the other additional comment in this bug, I'm back to leaning that the book is fine the way it is.
PAM is optional - If the user wants to use it, he'll need to do some reading and research to configure it properly. Additionally, the book would then also need instructions to configure the sshd_config file to enable PAM.
There's not many other packages that the book goes through a bunch of steps and instructions on how to configure *optional* dependencies, Courier and Postfix notwithstanding.
comment:3 by , 20 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Linux-PAM is listed as an optional dependency. We cannot address every optional dependency in the build instructions.
I believe this bug should be marked as 'invalid' because:
may need to install a PAM control file for sshd, otherwise password authentication may fail. Example PAM control files can be found in the contrib/ subdirectory"
<indecision>Though, as I wrote this, I'm thinking it probably wouldn't be a terrible thing to add some text about PAM in the SSH instructions.</indecision>
I'm posting to blfs.dev to get more input.