Odd behavior from passwd. Post: 303038999

Sponsored Content

Special Forums Cybersecurity Odd behavior from passwd. Post 303038999 by gull04 on Thursday 19th of September 2019 07:53:46 AM

09-19-2019

Registered User

Odd behavior from passwd.

Hi Folks,

Before I go off and start checking I'm just wondering if anyone has seen this behaviour before.

Code:

[root@fbakirpomd4 ~]# passwd e825390
Changing password for user e825390.
New password:
Retype new password:
Retype new password:
passwd: all authentication tokens updated successfully.

As you can see there is an extra "Retype new Password", the system is;

Code:

[root@fbakirpomd4 ~]# uname -a
Linux fbakirpomd4 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
[root@fbakirpomd4 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.5 (Maipo)
[root@fbakirpomd4 ~]#

The system has been built and a new "Security Standard" applied, this was done as a result of a "Security Audit" by a company called CGI.

This will cause an issue with a number of the standard accounts that we have on the servers going forward, the idea is to have a standard build so it has to be correct - one problem that I can foress is that the passwords are changed on the aforementioned accounts using an expect script and the second "Retype new Password" will break the script.

So I thought that I'd ask here before I raise an incident with Red Hat support.

Regards

Gull04

gull04

View Public Profile for gull04

Visit gull04's homepage!

Find all posts by gull04

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

even odd script

I need a unix script that check for even or odd. EXAMPLE:::: please enter the number to check: 12 the output: This is an even number it has to have prompts.

2. UNIX for Dummies Questions & Answers

Odd .sh behavior in script

Hello, I have been working on a what I thought was a fairly simple script for installing a software kit on Linux and Unix I am not new to scripting but am far from being fluent in sh scripting. any assistance would be appreciated. I have an odd bug occuring when executing the script. When...

3. HP-UX

Odd storage behavior

Hi, We have some troubles with our HP server (rx4640) running HP-UX 11.31. The server is attached to a JBod cabinet. If the JBod cabinet is powered on and we power on the server after then HP-UX can't find the devices (disks) at the cabinet. Does not help to run an ioscan -fnC disk. But if I power...

4. Shell Programming and Scripting

"Odd" behavior exiting shell script

Is it normal behavior for a shell script that terminates to terminate its parent shell when executed with the "." option? For example, if I have the example script (we'll name it ex.sh): #!/bin/sh if then echo "Bye." exit 2 fi And I execute it like this: >./ex.sh It...

5. UNIX for Dummies Questions & Answers

Finding the odd one out!

Hi guys, I wondered if someone would be able to help me. I have a number of files which all have entries in them looking something like; And I'm looking for a way where by I can compare a number of these files and identify the odd numbers in the sequence. So for example if I had to...

6. Solaris

passwd cmd reenables passwd aging in shadow entry

Hi Folks, I have Solaris 10, latest release. We have passwd aging set in /etc/defalut/passwd. I have an account that passwd should never expire. Acheived by emptying associated users shadow file entries for passwd aging. When I reset the users passwd using passwd command, it re enables...

7. AIX

When did AIX start using /etc/security/passwd instead of /etc/passwd to store encrypted passwords?

Does anyone know when AIX started using /etc/security/passwd instead of /etc/passwd to store encrypted passwords?

8. Solaris

Odd vi error

Hello, I have a weird think going on, on one of my servers. vi filename "/var/tmp" No such file or directory What going on here?

9. Programming

Odd behavior from GDB while trying to cross-debug an embedded Linux application.

Some background: The application normally runs on an embedded platform. Currently, for development purposes, I have the rootfs located @ /exports and the target is communicating over NFS. That way I can make a change on my local system, save the application @ /exports, and run the altered...

LEARN ABOUT CENTOS

schema-reload.pl

SCHEMA-RELOAD.PL(8)					      System Manager's Manual					       SCHEMA-RELOAD.PL(8)

NAME

       schema-reload.pl - Directory Server perl script for updating the schema.

SYNOPSIS

       schema-reload.pl [-Z serverID] [-D rootdn] { -w password | -w - | -j filename } [-P protocol] [-d schemadir] [-v] [-h]

DESCRIPTION

       Manually reloads the schema files used by the Directory Server instance, either in the default location, or in user-specified locations.

OPTIONS

       A summary of options is included below:

       -Z Server Identifier
	      The server ID of the Directory Server instance.  If there is only one instance on the system, this option can be skipped.

       -D Root DN
	      The Directory Manager DN, or root DN.  If not specified, the script will search the server instance configuration for the value.

       -w password
	      The rootdn password.

       -w -
	      Prompt for the rootdn password.

       -j password filename
	      The name of the file that contains the root DN password.

       -d schemadir
	      Gives  the full path to the directory where the schema file is located. If this is not specified, the script uses the default schema
	      directory, /etc/dirsrv/schema.

       -P protocol
	      The connection protocol to connect to the Directory Server.  Protocols are STARTTLS, LDAPS, LDAPI, and  LDAP.   If  this	option	is
	      skipped, the most secure protocol that is available is used.  For LDAPI, AUTOBIND is also available for the root user.

       -v
	      Display verbose ouput

       -h
	      Display usage

EXAMPLE

       schema-reload.pl -Z instance3 -D 'cn=directory manager' -w password -P STARTTLS -d /LDAP/schema/

	      Note:  security  must be enabled to use protocol STARTTLS.  If STARTTLS is not available it will default to next strongest/available
	      protocol automatically.

DIAGNOSTICS

       Exit status is zero if no errors occur.	Errors result in a non-zero exit status and a diagnostic message being written to standard error.

AUTHOR

       schema-reload.pl was written by the 389 Project.

REPORTING BUGS

       Report bugs to http://bugzilla.redhat.com.

COPYRIGHT

       Copyright (C) 2013 Red Hat, Inc.

								    Mar 5, 2013 					       SCHEMA-RELOAD.PL(8)