Bug 2232317
| Summary: | gnome-terminal echos sensitive commands | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | zorrodino |
| Component: | gnome-terminal | Assignee: | Matthias Clasen <mclasen> |
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | amigadave, gnome-sig, mclasen, philip.wyett, rstrode |
| 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: | 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
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 |