unable to set password with modprpw

[modprpw]

Not able set random generated passwd with
modprpw -x

Will not return anything back, expect to put a random generated password string.

This happens even when a new user is added to the system.

[A. Clay Stephenson]

It rather difficult to help when you don't bother to identify your OS. The -x option works for me under 11.11 (as long as you don't do it for user root). -x output the plaintext passwd to stdout, install the password hash, and expires the password so that the user must immediately change his password after logging in.

[A. Clay Stephenson]

It's rather difficult to help when you don't bother to identify your OS. The -x option works for me under 11.11 (as long as you don't do it for user root). -x output the plaintext passwd to stdout, install the password hash, and expires the password so that the user must immediately change his password after logging in.

[Steven E. Protter]

Shalom,

Not just an itrc member, but a system utility? Consider changing your profile name. It confused me. Its late here.

There must be an error in /var/adm/syslog/syslog.log

Something is not set up properly or missing or has the wrong permissions.

After executing the command, try this:
echo $?

Thats the process return code. I'm betting its not zero and can provide a clue to what is going on here.

Seems its mystery night(IST) on ITRC.

SEP

[Jeff Schussele]

Hi,

Did you check to see whether an existing user's tcb entry has been modified - i.e the date/time stamp is the time you ran the command?

Also you may have a system-wide user PW policy set that only allows user-specified PWs or denies system-generated PWs.
Check your /tcb/files/auth/system file - specifically the u_genpwd, u_genchar & u_genletters fields.

HTH,
Jeff

[modprpw]

I am using 11.11
return code after running command %modprpw -x is 126

[A. Clay Stephenson]

The strange thing is that a return of 126 is not even listed. I would do a getprpw of this same user to see if you are able to extract the field. This really sounds like a corrupt tcb entry.

The other thing I notice is your "%" -- probably indicating the dreaded C shell. I would rerun your command under the POSIX shell.

[A. Clay Stephenson]

The strange thing is that a return of 126 is not even listed. I would do a getprpwd of this same user to see if you are able to extract the field. This really sounds like a corrupt tcb entry.

The other thing I notice is your "%" -- probably indicating the dreaded C shell. I would rerun your command under the POSIX shell.

[modprpw]

This is not happening to any individual users, even if I create a user and try to modprpw -x samething is happening
(no passwd string is generated).

I am using sh, ksh and same

[A. Clay Stephenson]

Okay, I am going to ask a very dumb question. Is this a trusted system?

[modprpw]

Yes, It is trusted system. This is very valid question.