5 ms·
>All crash dump types, including heap dumps and full dumps. Maybe I should not have used Windows Insider after all which forces you to have it on full...
by chrisper 10y ago
>All crash dump types, including heap dumps and full dumps.
Maybe I should not have used Windows Insider after all which forces you to have it on full...
- doubleplusgood 10y agoI could consider a scenario where heap dumps of a process crashing due to an exploit would be immensely helpful to Microsoft, since everyone is essentially now a honeypot-esque collector. There needs to be an off switch for this, though.
- simion314 10y agoWow, this means they will store in their databases your private data you had in RAM when something or Windows crashed? Am I wrong? because this sounds horrible, you should have an option on sending your memory dumps.
- chrisper 10y agoYes, you are right. I wonder how this affects something like Keepass. If I had it unlocked open while Windows crashed, does Microsoft now have all my passwords?
- sqeaky 10y agoYes it means microsoft has your passwords and you have technical recourse. If you attempt to use legal recourse you will likely fail and your passwords could become publicly viewable evidence. Change your passwords and don't store them on a close sourced system, this is the only mitigation I see you having that is sure to work.
- chrisper 10y agoActually, if you look here [1], it says: >While KeePass is running, sensitive data (like the hash of the master key and entry passwords) is stored encryptedly in process memory. This means that even if you would dump the KeePass process memory to disk, you could not find any sensitive data. Either way, it is bad that Microsoft does not really warn people about this. [1] http://keepass.info/help/base/security.html#secmemprot http://keepass.info/help/base/security.html#secmemprot