Craig Vorwald said: Maybe it has something to do with the age of the files??
Quicken data files SHOULD be encrypted (using at least AES-128)!
For years, I've incorrectly assumed that Quicken data files were properly encrypted. Honestly, I feel deceived.
All aspects of Quicken software should meet or exceed industry standards for the security of financial data.
But, let's not go overboard. Requiring 2 Factor Authentication or causing Quicken to lock out after 5 minutes of inactivity would be taking things a little too far. Some people might actually like those options, which would be fine as long as they are optional. Quicken still needs to remain usable.
If file encryption were available, I'd certainly take advantage of it.
I think Quicken files should be encrypted, and like most other encrypted data performed by other programs, it is up to the user to worry about recovery of the encrypted data. I don't even trust cloud data management and encrypt any data before sending it to the cloud, like google cloud for example. Google and other cloud services make no promises of remedial compensation if cloud data was compromised by a bad actor on their side.
I can perform a Unix "strings" command on a quicken datafile and the first readable string that appears is the Quicken user online account login. Security names and the filenames also appear. Old email addresses and login id's for other websites also appear, which I suspect are from the Quicken address book. It is pretty hard to decipher the contents of a Quicken datafile.