Timeline for Password shown on screen after crash on Linux, any idea why?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2018 at 16:50 | comment | added | Gjordis | If some other application (like in this case) logs, prints or caches insecurely some sensitive information, THEN apport is/was in risk of exposing them. But this requires and underlying badly designed software or a glitch. Apport does not handle passwords or password-inputs in any way unless its a part of the dump or log. | |
| Jun 20, 2018 at 12:52 | comment | added | forest | @mootmoot What is being displayed on the screen is a regular kernel oops/panic/whatever, it has nothing to do with Apport. | |
| Jun 20, 2018 at 12:41 | comment | added | mootmoot | @Gjordis than this is obvious Apport issue. | |
| Jun 20, 2018 at 12:40 | history | edited | mootmoot | CC BY-SA 4.0 | added 4 characters in body |
| Jun 20, 2018 at 12:33 | comment | added | Gjordis | There is no confusion. The password shown on the console is my userpassword which is no way used with my encrypted LVM, and only used the open the Gnome-keyring containing the actual home-directory ecryptfs password | |
| Jun 15, 2018 at 12:49 | history | edited | mootmoot | CC BY-SA 4.0 | added 234 characters in body |
| Jun 15, 2018 at 8:56 | comment | added | Gjordis | But why would apport itself have access to my password? I think the Apport case is for cases where some other process prints or stores the password and it gets included in the dump. | |
| Jun 15, 2018 at 7:07 | history | answered | mootmoot | CC BY-SA 4.0 |