Paul

How does this make your default pattern more secure? Are you not using a long and random password? Assuming the attacker also knows which site and what logon you use, then you have probably already lost your secrets. cheers, Paul

That error suggests Defender doesn't like the snapshot, probably because it is a snapshot build and Defender is being cautious - which is good. A new snapshot build will not fix this. Revert to KeePass 2.60 and wait for the next KeePass release which will incorporate the changes. cheers, Paul

Why are you making this more complex? KeePass is already very secure and I see no improvement in your suggestions. Adding multiple key decryption seems like a nice idea but it adds complexity and potential exposure via the other keys, without adding functionality. cheers, Paul

You need to test onedrive by putting a text file in the same location and see how long it takes to show on your Android. Then edit the file and see how long it takes to change on the Android. If it doesn't change then you are doing something wrong on onedrive. cheers, Paul

You can't brute force a KeePass database if you have reasonable database encryption settings and a strong password. Even a weak password would take years with reasonable settings. See the GRC Password Haystack page and enter a strong password. Assume the bad guys get lucky and guess the correct answer in 10% of the time it takes for a full search, then add one character to the password and compare. Basically, a longer password is much more secure than a shorter but more complex password. cheers,...

Press Ctlr F (full search). UUID is off by default in full search. cheers, Paul

As there is no support on Sourceforge and the MC website seems to be MIA, I'm not sure we can help. BTW, why do you want a second cipher? One (AES) is secure enough for US gov top secrets. cheers, Paul

600MB is nothing unless you are very RAM restricted (4GB). You could try using a direct link to access the file. The alternative is webdav (not on Dropbox). cheers, Paul