I really, really don't want to discuss the recent article about decrypted stuff hanging around in memory after locking 1Password. That's been discussed to death already. Please don't chime in to discuss the issue in general terms.
What I want to know is this:
Since 1Password doesn't have a feature to automatically exit the application and close the process after a period of not being used, I am making a scheduled task in Windows that will automatically force-kill the 1Password process when my computer locks (at work) or when my computer sits idle for a half-hour or so (at home).
I notice there are usually 2 1Password processes running, if I have interacted with 1Password at all (not even having logged in yet):
u:\>tasklist /v /fi "IMAGENAME eq 1Password.exe" /FO list Image Name: 1Password.exe PID: 17052 Session Name: Console Session#: 1 Mem Usage: 23,332 K Status: Running User Name: DOMAIN\me CPU Time: 0:00:00 Window Title: OleMainThreadWndName Image Name: 1Password.exe PID: 19792 Session Name: Console Session#: 1 Mem Usage: 90,740 K Status: Running User Name: DOMAIN\me CPU Time: 0:00:01 Window Title: Hidden Window
The second process changes its Window Title, depending on what I am doing with 1Pasword, the first remains the same. Furthermore, if I choose "Exit" from the 1Password menu, the second process goes away, only leaving the process with window title "OleMainThreadWndName".
If I kill both processes (taskkill /F /FI "IMAGENAME eq 1Password.exe"), obviously all my secrets get removed from memory (eventually). However, doing that makes the browser extension button grayed out and unusable until I manually launch 1Password again, so I'd rather just kill the 2nd process if I can (taskkill /F /FI "IMAGENAME eq 1Password.exe" /FI "WINDOWTITLE ne OleMainThreadWndName"). So, my questions are:
Yes, I know the risk is fairly low. I just want that little bit of extra protection for my own peace of mind.
1Password Version: 7.3.657
Extension Version: 22.214.171.124
OS Version: Windows 10
Sync Type: Not Provided