Skip to Content
+1 (888) 578-8743[email protected]
Ringing Liberty

Ringing Liberty

Freedom through Communications

Home Operations Operations /etc/login.defs settings not taken into account: password aging

/etc/login.defs settings not taken into account: password aging

on July 6, 2021July 6, 2021by

David asked:

The following is done on a Ubuntu 20.04 system.

This is the scenario where I am facing an issue:

  • I edit the password aging settings in the login.defs file
  • Then I change the password of the user with passwd user command
  • I check what settings were applied to the password of the user with the chage -l user command

The issue:

The values returned seem not to be taking into account the changes made to the /etc/login.defs file.

Is there any reason for this?

How could I debug the issue? (e.g.: how to see what other settings may be tampering the values from the /etc/login.defs?)

Thank you!

My answer:


The man page is pretty clear about this:

        PASS_MAX_DAYS, PASS_MIN_DAYS and PASS_WARN_AGE are only used at the
        time of account creation. Any changes to these settings won't affect
        existing accounts.

View the full question and any other answers on Server Fault.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

configurationdebuggingloginpamubuntu

Post Navigation

fail2ban wont start/Python syntax error
How to Avoid Crazy Caching with "Vary: Cookie" Header in NGINX

Related Post

NGINX SSL Certificate based on URI

Qemu TRIM and discard on a physical SSD device

How does the Profile Manager send Clear Passcode command get to the iDevice?

Write to the stdin of a running process with the same effect/behaviour of directly writing

Postfix Refused on 587

Is it useful to deploy OpenStack to a single node?

Latest Posts

  • CentOS yum-cron updates stability
  • Best solutions for auto deployment of multiple server applications
  • Does the OS stop all PIDs before restarted when the user clicks restart in Ubuntu?
  • How to get the remote hostname resolved through DNS when using Nginx and ModSecurity?
  • tcpdump output has a different hostname

Recent Comments

  • kg on Matching autonomous system numbers in iptables
  • Alex on Matching autonomous system numbers in iptables
  • How do I get puppet master to listen on IPv6? - Ringing Liberty on Making Puppet Enterprise 3.7 work with IPv6
  • Dan on Matching autonomous system numbers in iptables
  • JohnnyB on Making Puppet Enterprise 3.7 work with IPv6

Tags

amazon-ec2 amazon-web-services ansible apache-2.2 apache-2.4 bash cache centos centos6 centos7 configuration debian docker domain-name-system email email-server fedora firewall iptables ipv6 kvm-virtualization linux linux-networking mysql networking nginx php php-fpm postfix redhat redirect reverse-proxy rpm security selinux smtp ssh ssl systemd ubuntu virtual-machines virtualization windows wordpress yum

About Ringing Liberty

Ringing Liberty is the personal web site of Michael Hampton, a professional system administrator.

Email: [email protected]
Phone: +1 888 578-8743

© Copyright 2022 Ringing Liberty. All Rights Reserved. Blossom Consulting | Developed By Blossom Themes. Powered by WordPress.Privacy Policy