Option: Nuke downloaded files after exiting file management mode

[alanrick]

[Feature Request] Some of the files I store on Mooltipass contain sensitive information that I want to inspect but don't want left on the PC. That's why I store the file on mooltipass in the first place.

Currently, after downloading to inspect the contents I have to remember to delete the file from the PC and then again from the PC's garbage bin. (Windows)

I would prefer mooltipass to download in a mooltipass-specific folder and that the contents of this folder are wiped when I exit File Management Mode. If I really want to keep the file on the PC (e.g. certificate) then all I'd need to do is copy it to another folder before leaving File Management Mode.

[limpkin]

@azubieta : would you be able to add an "eye icon" next to the "floppy disk icon" that

• would trigger the very same download action
• not offer to specify a place to download the file
• instead, create a temporary file named after the name of the service
• trigger OS file opening
• delete file after the file is closed

@raoulh is that technically feasible? monitoring when the triggered process is done with the provided file?

[azubieta]

We should also overwrite the file content with 0 to avoid recovering.

Monitoring opened files depends on the file system and the OS. So it will not be easy to achieve and we will have to make an implementation for every platform.

[alanrick]

delete file after the file is closed

or after file management is closed. That might be easier and less OS-dependent to monitor as @azubieta explains. Also, the directory path should be constant and known, so that it can be excluded from automatic backups.

[raoulh]

What kind of file type are those?

For simple text file, you could use mc-cli in a console:

➜  ~ mc-cli data get my_context
My secret text

For a wider approach in MC, this could be not so easy to implement. The problem is that files could be locked, copied etc by the running application, and depending of the OS. Let say you have a .doc word file. Word will lock the file, and create some backup somewhere. We cannot know if the file is in use on not. On a unix system files can be deleted, but some app rewrite them at some point (auto backup feature or so).

[alanrick]

What kind of file type are those?

In my case txt files. Perhaps jpg. I understand the locking problem. Displaying the txt or jpg contents would be an alternative to downloading.

Another alternative might be configuring a fixed "secret" directory where they're downloaded so that I always know where to look after downloading. And a mooltipass indicator (icon) to show that the directory contains files. That would avoid problems with sloppy pc habits (e.g. downloading to somewhere unusual and forgetting where)

[raoulh]

For text mc-cli would work, and for jpg piping the output to an image viewer would work too!

[alanrick]

Thanks @raoulh , I've figured it out and the mc-cli workaround does work. But I'd still prefer the nuking or display within moolticute. btw mc-cli data get suffers the same issue as #187