Re: TSM Linux scheduler fails authentication when a certain VALID password is used!?
2002-03-21 17:56:21
Subject: |
Re: TSM Linux scheduler fails authentication when a certain VALID password is used!? |
From: |
"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU> |
Date: |
Thu, 21 Mar 2002 17:38:14 -0500 |
I think this is a known bug:
Item IC31516
APAR Identifier ...... IC31516 Last Changed..02/02/22
PASSWORDACCESS GENERATE DOES NOT WORK IF ENCRYPTION OF THE
PASSWORD CAUSES A ZERO BYTE TO BE PART OF THE PASSWORD.
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 2 Date Closed ......... 01/09/06
Component .......... 5698TSMCL Duplicate of ........
Reported Release ......... 42N Fixed Release ............ 999
Component Name TIVOLI STR MGR Special Notice
Current Target Date ..01/12/30 Flags
SCP ................... UNIX
Platform ............ UNIX
Status Detail: Not Available
PE PTF List:
PTF List:
Release 42N : PTF not available yet
Release 42A : PTF not available yet
Release 42H : PTF not available yet
Release 42S : PTF not available yet
Release 42L : PTF not available yet
Release 42X : PTF not available yet
Release 42T : PTF not available yet
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
Whe using passwordaccess generate, a password record is formed
for writing to the tsm.pwd file. The password record consists
of the userid, servername, nodename, and the encrypted password.
All parts of the password record are written as a sring and the
encrypted password will fail to be written correctly if the
string contains a 0-byte within it.
for example if the encrypted password string is:
"D8 D6 BD 00 94 26 CB 11 7F" when it is written to the
password record, it is truncated at the 0-byte to "D8 D6 BD"
and is thus incorrect within the tsm.pwd.
This problem will only occur with passwordaccess generate
and the password encryption scheme results in a 0 symbol
within it. Since the password is incorrect in the tsm.pwd file,
the user will be prompted for the password even if it was
already set using passwordaccess generate.
.
This problem also applies to the Netware user id and associated
password, which can be saved in the tsm.pwd file if the option
"nwpwfile yes" is specified in the dsm.opt file.
LOCAL FIX:
Use a different nodename and/or password so the encryption
scheme will generate a different encryption string that does
not contain an 0 within it.
PROBLEM SUMMARY:
****************************************************************
*USERS AFFECTED: Novell Netware client, UNIX client *
****************************************************************
*PROBLEM DESCRIPTION: PASSWORDACCESS generate: incorrect *
* writing to the password file *
****************************************************************
PROBLEM CONCLUSION:
The problem was related with an incorrect way of the password
record writing. It should be written as the binary data rather
than the string.On Netware client the problem can occur
both for TSM and Netware (TSA) passwords.
TEMPORARY FIX:
Try to use another TSM/TSA password or another node/NW user id.
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: TSM Linux scheduler fails authentication when a certain VALID password is used!?,
Prather, Wanda <=
|
|
|