Hello,
some time ago I reported a problem with the linux 4.2 client. The
passwordaccess generate option doesn't work under certain circumstances.
There is now a apar which diescribes the problem:
APAR Identifier ...... IC31516      Last Changed ........ 01/09/06
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.


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 rathe
than the string.

TEMPORARY FIX:
Try to use another password or another node


Best regards
Gerhard

----
Gerhard Rentschler                   email:
Gerhard Rentschler                   email:
g.rentschler AT rus.uni-stuttgart DOT de
Manager Central Servers & Services
Regional Computing Center   tel: ++49/711/6855806
University of Stuttgart                fax: ++49/711/682357
Allmandring 30a
D 70550 Stuttgart
Germany