On 08/26/2018 10:47 AM, spiky0011 wrote:
On 26/08/2018 16:39, Bruce Dubbs wrote:
On 08/26/2018 09:37 AM, spiky0011 wrote:
When building Linux Pam Without Cracklib, there are 2 options for
/etc/pam.d/system-password.
If you have to install cracklib later in book after initial build i,e
libpwquality you need cracklib which tells you to rebuild shadow, but
the /etc/pam.d/system-password is unchanged.
Would there be an option to put the cracklib
/etc/pam.d/system-password file somewhere else or some sort of note
about it.
It's a text file. You can always overwrite the old with a new version.
Are you suggesting some text changes in the book? If so, what explict
changes?
-- Bruce
Installing cracklib later in build, there isn't a reference to the
Linux Pam file, so If you built shadow without Cracklib you create the
1 " system-password file" build cracklib > shadow you need to be
reference to changing the system-password file.
Yes it is only a file and is changeable IF you know about it, or you
forgot about it.
If you build cracklib after pam, then the result is that pam will not
use cracklib. Cracklib is used for Kerberos, libpwquality, and shadow
as well as pam. It's possible that the user does not want pam to use
cracklib.
I don't think we want to get into the situation where we say something
like "This packages was optional when you installed package X. After
you install this, you need to reinstall package X to use it there."
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
