Peter Kara

I agree with previous posts, if you verify you have the official download, considering you are using a widely used open source program, that is about as safe a program to install as any out there. The warning references the Norton Data Protector feature. Here is more information about that. It is configureable. https://support.norton.com/sp/en/us/home/current/solutions/v130571264

I agree with previous posts, if you verify you have the official download, considering you are using a widely used open source program, that is about as safe a program to install as any out there. The warning references the Norton Data Protector feature. It simply monitors for changes to a set of files and directories that you tell it to monitor (there may be a default set, but it's configurable). https://support.norton.com/sp/en/us/home/current/solutions/v130571264

Good practices are that your keyfile should be local, not on the same cloud storage provider where the kdbx is. So IF the act of updating onedrive actually made a difference, that means they must have had the keyfile stored on onedrive along with the kbdx... which again is bad practice. BUT I suspect it's nothing to do with the update. Figure out where the keyfile really is and tell keepass to look there. Once you get through all that and figure out where your keyfile is, for the future is make sure...

Good practices are that your keyfile should be local, not on the same cloud storage provider where the kdbx is. So IF the act of updating onedrive actually made a difference, that means they must have had the keyfile stored on onedrive along with the kbdx... which again is bad practice. BUT I suspect it's nothing to do with the update. Figure out where the keyfile is and tell keepass to look there.

Good practices are that your keyfile should be local, not on the same cloud storage provider where the kdbx is. So IF the act of updating onedrive actually made a difference, that means they must have had the keyfile storedi with the kbdx which again is bad practice. BUT I suspect it's nothing to do with the update. Figure out where the keyfile is and tell keepass to look there.

Good practices are that your keyfile should be local, not on the same cloud storage provider where the kdbx is. So IF the act of updating onedrive actually made a difference, it means you had the keyfile storedi n a bad place. But I suspect it's nothing to do with the update. Figure out where the keyfile is and tell keepass to look there.

Most modern chromebooks allow you to set up one or more linux containers. You can install a desktop linux keepass program onto there (either keepassXC or the original keepass version 2). It won't integrate well with the chromeOS browser since the container isolation prevents the chrome browser extension from working and prevents autotype from working. But you can still read the passwords and type them, or cut and paste using clipboard. If you want, you could install a browser of your choice into...

Most modern chromebooks allow you to set up one or more linux containers. You can install a desktop linux keepass program onto there (either keepassXC or the original keepass version 2). It won't integrate well with the chromeOS browser since the container isolation prevents the chrome browser extension from working and prevents autotype from working. But you can still read the passwords and type them, or cut and paste using clipboard. If you want, you could install a browser of your choice into...