text: Title: Passwords are stored plain text in logs [Bug] 
  Body: ### Product Version
  
  3.10.13
  
  ### Product Edition
  
  - [X] Community Edition
  - [ ] Enterprise Edition
  - [ ] Enterprise Trial Edition
  
  ### Installation Method
  
  - [X] Online Installation (One-click command installation)
  - [ ] Offline Package Installation
  - [ ] All-in-One
  - [ ] 1Panel
  - [ ] Kubernetes
  - [ ] Source Code
  
  ### Environment Information
  
  Operating System: Ubuntu 20.04
  Shell: Bash
  
  ### 🐛 Bug Description
  
  The issue occurs when users are connected to a Linux system via JumpServer (using SSH key authentication), and then need to input passwords within the session for specific commands. For example:
  
      When switching to a root user using the su - command, the root password is logged in cleartext within the session logs.
      When connecting to a database using mysql -u root -p, the password entered is also logged in cleartext.
  
  This poses a significant security risk, as sensitive information such as passwords should not be captured or logged in plain text within session logs.
  
  ### Recurrence Steps
  
  Log into JumpServer.
  Use SSH key-based authentication to connect to a Linux system.
  Once connected, run a command that prompts for a password, such as:
  
      su - (to switch to root)
  
  
  Enter the password when prompted.
  Review the session logs in JumpServer and observe that the entered password is logged in cleartext.
  
  ### Expected Behavior
  
  Password inputs, such as those for su - or mysql -u root -p, should not be captured or stored in cleartext within JumpServer session logs. Password fields should be masked or excluded from logs entirely to protect sensitive information.
  
  ### Additional Information
  
  _No response_
  
  ### Attempted Solutions
  
  _No response_