Bug 2232317

Summary:	gnome-terminal echos sensitive commands
Product:	[Fedora] Fedora	Reporter:	zorrodino
Component:	gnome-terminal	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	37	CC:	amigadave, gnome-sig, mclasen, philip.wyett, rstrode, zorrodino
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-01-15 12:21:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description zorrodino 2023-08-16 09:44:39 UTC

Gnome terminal echos the command being executed in the tab/terminal title regardless of the settings.

This is a problem for me because occasionally I run scrips which require a password as an argument.
For example: az login -u .... -p #####
I start these commands with the HISTIGNORE value of course.

The problem is that this behaviour appears inescapable.
Changes to PROMPT_COMMAND and PS1 do not seem to achieve anything.
Changes in settings do not seem to achieve anything.

The problem persists when using bash --norc.

Reproducible: Always

Steps to Reproduce:
1. Open gnome-terminal
2. Run: yes "mypassword"
3. See yes mypassword in terminal title and tab title
Actual Results:  
See yes mypassword in terminal title and tab title

Expected Results:  
Ability to hide sensitive commands

Comment 1 zorrodino 2023-08-16 09:48:44 UTC

The reason I made this a medium bug is that one can work-around the problem. It is, however, very annoying and a security concern if somebody isn't well aware of this.

Setting the command to know what the terminal is running is not bad per-se, BUT there should be some better way to protect sensitive commands

Comment 2 Aoife Moloney 2023-11-23 01:49:12 UTC

This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2024-01-15 12:21:08 UTC

Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.