G06.31 Release Version Update Compendium

Manageability Products
G06.31 Release Version Update Compendium—544625-001
6-4
Fallback
The mitigation procedure is:
1. Use VPROC to determine the current versions of:
•
OSMP
•
OSMON
•
SAFEART
•
SAFECOM
2. Back up current Safeguard files ($*.SAFE.*, $SYSTEM.SYSTEM.USERID, and
$SYSTEM.SYSTEM.USERAX).
3. Use SAFECOM to build an Obey file to save the current policy:
TACL> safecom/out $system.safe.safevalu/
=display as commands on
=info safeguard, detail
The output from these commands is retained in the SAFEVALU file located at
$SYSTEM.SAFE.
Once the new version of Safeguard is installed and you want to retain your original
Safeguard values, run the SAFEVALU Obey file created in Step 3 in SAFECOM to
restore the orginal Safeguard values.
You can restore the files backed up in the previous steps if any unexpected failures
occur during migration.
If you do not follow these steps and you wish to restore the original default values,
then, once the new version of Safeguard is installed, use SAFECOM to modify the
appropriate attributes.
For more details, see Section 10 of the Safeguard Administrator's Manual.
Fallback
Longer passwords and embedded spaces in passwords are not supported in pre-
G06.31 RVUs. Any user with a password that exceeds 8 characters or contains
embedded spaces will be unable to login after fallback.
From the G06.31 RVU, you can fall back to the G06.29 or G06.30 RVU.
Considerations for falling back to a previous RVU in a Safeguard or Standard Security
environment are:
•
The super ID password must not exceed 8 characters and must not contain
embedded blanks. If these conditions are not met, The super ID password must be
changed accordingly; otherwise, the super ID will be unable to logon after falling
back.
•
If the PASSWORD-MINIMUM-LENGTH attribute value exceeds 8, the system
administrator must change it to a value less than 8 using SAFECOM in a
Safeguard environment or PWCONFIG in a Standard Security environment.