| 2016-08-20 20:02:05 |
Damian Pereira |
description |
Steps to reproduce:
* Create a 7zip encrypted file, password protect it.
* Open that file with Archive Manager
* Open a text file with scratch, edit it and update if you want to.
* Close scratch.
* Close Archive manager.
* Open scratch again, cached version of file will still be there, even if the original encrypted file was closed.
I think it would be nice if Archive manager tried to delete the cache or told the user that these cached files are still there. I might try to edit SecretInformation.txt inside the 7z file, close everything and then next person comes in, opens text editor and can still see the cached version without having a password.
Not sure how important is the use-case of editing encrypted 7z as an encrypted folder, but if it is intended to be secure then this is clearly a bug. |
Steps to reproduce:
* Create a 7zip encrypted file, password protect it.
* Open that file with Archive Manager
* Open a text file with scratch, edit it and update if you want to.
* Close scratch.
* Close Archive manager.
* Open scratch again, cached version of file will still be there, even if the original Archive Manager window was closed.
I think it would be nice if Archive manager tried to delete the cache or told the user that these cached files are still there. I might try to edit SecretInformation.txt inside the 7z file, close everything and then next person comes in, opens text editor and can still see the cached version without having a password.
Not sure how important is the use-case of editing encrypted 7z as an encrypted folder, but if it is intended to be secure then this is clearly a bug. |
|
