Open krasen11 opened 3 months ago
Thanks for the report. Can you turn on protocol and message debuggers so that we can determine what's on the screen? https://github.com/zowe/tn3270-ng2/wiki/Loggers#developingdebugging The terminal usually handles invisible fields, so it could be that there's some additional way to hide this field that will show up in the log and then we can make an improvement.
Buffer content from QWS3270 tracing displayed via REXX (this can be tested anywhere):
/* rexx */
HX3270 = "01c51106402903c0e842f7410040c9c5",
"c5f1f8f7c940c5d5e3c5d940d3d6c7d6",
"d540d7c1d9c1d4c5e3c5d9e240404040",
"40404040404040404040404040404040",
"40404040404040404040404040404040",
"40404040404040404040404011069040",
"2903c07042f44100d3d6c7d6d5004040",
"40404040404000d7c1e2e2e6d6d9c400", /* PASSWORD */
"40404040404040404040404040404040",
"40404040404040404040000000000000",
"00000000000000000000000000000000",
"0000000000000000c7d9d6e4d7004040",
"40404040404000e2c5c3d3c1c2c5d300",
"40404040404040400000000000000000",
"00000000000000000000000000000000",
"00000000000000000000000000000000",
"000000000000110698131106902903c0",
"6042f441001106972903c04042f44100",
"1106a02903c07042f441001106a92903",
"c04c42f441001106c42903c07042f441",
"001106e12903c07042f441001106e729",
"03c04042f441001106f02903c07042f4",
"41001106f92903c04042f44100110702",
"2903c07042f44100ffef01c2ffef"
say x2c(HX3270)
Because of screen size, the output is malformed, but
PA
) is not displaying characters
PASSWORD
has no special attributes, the solution will be somewhere else in the buffer.
Describe the bug Hello, We are using TN3270 terminal in Zowe Desktop to sign in SMCS console but the password is visible on the screen(Screen shot3). To prevent of possible security bridge password should be invisible on the screen. Please take a look and assist. Thanks in advance.
Expected behavior Password should stay invisible on the screen.
Screenshots
Logs n/a
Details
build and hash: v2.x/master#2474
Web Browser Details (if the bug relates to Zowe Desktop usage):
REST API client (in case of REST API issue): n/a
Shell Environment Details (if the bug relates to CLI): n/a Additional context Add any other context about the problem here.