Re: [LFS Trac] #5838: shadow-4.19.0

"LFS Trac" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <[email protected]>
#5838: shadow-4.19.0
-------------------------+-----------------------
 Reporter:  Bruce Dubbs  |       Owner:  lfs-book
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  12.5
Component:  Book         |     Version:  git
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------
Comment (by Bruce Dubbs):

 Release 4.19.0

 Breaking changes:

     Remove support for escaped newlines in configuration files.
     It never worked correctly.
     b0a7ce5 (2025-12-05; "lib/, po/: Remove fgetsx() and fputsx()")

     Some user names and group names are too dangerous and are rejected,
     even with --badname.
     25aea74 (2025-12-25; "lib/chkname.c, src/: Strictly disallow really
 bad names")

 Future breaking changes:

     SHA512 and SHA256 will be supported unconditionally in the next
     release. The build-time flag '--with-sha-crypt' will be removed.

 Support:

     Several years ago, there were talks about deprecating su(1) and
     login(1), back when this project was maintained as part of Debian.
     However, nothing was clearly stated, and there were doubts about the
     status of these programs. Let's clarify them now.

     Our implementations of su(1) and login(1) are fully supported, and we
     don't have any plans to remove them. They are NOT deprecated.

 Deprecations:
 {{{
     groupmems(8)
     The program will be removed in a future release.

     logoutd(8)
     The program will be removed in the next release.

     DES
     This hashing algorithm has been deprecated for a long time,
     and support for it will be removed in a future release.

     MD5
     This hashing algorithm has been deprecated for a long time,
     and support for it will be removed in a future release.

     login.defs(5): MD_CRYPT_ENAB
     This feature had been deprecated for decades. It will be
     removed in a future release.
     The command-line equivalents (-m, --md5) of this feature in
     chpasswd(8) and chgpasswd(8) will also be removed in a future
     release.

     login.defs(5): PASS_MAX_LEN
     This feature is ignored except for DES. Once DES is removed,
     it makes no sense keeping it. It may be removed in a future
     release.
 }}}

 {{{
 Modern security standards, such as NIST SP 800-63B-4 in the USA,
 prohibit periodic password expiration.
 https://pages.nist.gov/800-63-4/sp800-63b.html#passwordver
 https://pages.nist.gov/800-63-FAQ/#q-b05
 https://www.ncsc.gov.uk/collection/passwords/updating-your-
 approach#PasswordGuidance:UpdatingYourApproach-
 Don'tenforceregularpasswordexpiry
 }}}

 To align with these, we're deprecating the ability to
 periodically expire passwords. The specifics and long-term
 roadmap are currently being discussed, and we invite feedback
 from users, particularly from those in regulated environments.

 {{{
 This deprecation includes the following programs and features:

  expiry(1)
  chage(1):
          -I,--inactive (also the interactive version)
          -m,--mindays (also the interactive version)
          -M,--maxdays (also the interactive version)
          -W,--warndays (also the interactive version)
  passwd(1):
          -k,--keep-tokens
          -n,--mindays
          -x,--maxdays
          -i,--inactive
          -w,--warndays
  useradd(8):
          -f,--inactive
  usermod(8):
          -f,--inactive
  login.defs(5):
          PASS_MIN_DAYS
          PASS_MAX_DAYS
          PASS_WARN_AGE
  /etc/default/useradd:
          INACTIVE
  shadow(5):
          sp_lstchg: Restrict to just the values 0 and empty.
          sp_min
          sp_max
          sp_warn
          sp_inact
 }}}

 We recognize that many users operate in environments with
 regulatory or contractual requirements that still mandate
 password aging. To minimize disruption, these features will
 remain functional for a significant period. However, we
 encourage administrators to review their internal policies,
 talk to their regulators if appropriate, and participate in the
 roadmap discussion linked above.
-- 
Ticket URL: <https://wiki.linuxfromscratch.org/lfs/ticket/5838#comment:1>
LFS Trac <https://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.