|
Problem IT34404
|
Status: Closed |
CONNECTION PROPERTIES VALUE FOR A PASSWORD SHOULD NOT BE IN READABLE FORMAT
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
In Informix-HQ 1.2.0, under the Servername ----> setup
When a Connection Property for a Password field is given, the
value which we enter in as password is Readable.
This value should not be visible. It should be shown as asterick
characters. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of informixHQ prior to Informix 14.10.FC5. *
****************************************************************
* PROBLEM DESCRIPTION: *
* In Informix-HQ 1.2.0, under the Servername ----> setup *
* *
* When a Connection Property for a Password field is given, *
* the *
* value which we enter in as password is Readable. *
* This value should not be visible. It should be shown as *
* asterisk *
* characters. *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of informixHQ prior to Informix 14.10.FC5. *
****************************************************************
* PROBLEM DESCRIPTION: *
* In Informix-HQ 1.2.0, under the Servername ----> setup *
* *
* When a Connection Property for a Password field is given, *
* the *
* value which we enter in as password is Readable. *
* This value should not be visible. It should be shown as *
* asterisk *
* characters. *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Comment |
Upgrade to Informix 14.10.FC5. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.09.2020
10.12.2020
10.12.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
