develop1

I tend to always use the feature "autotype selected entry" which performs a "pull" the desired credentials (the currently highlighted keepass record) into current window. The above feature does not have a hot key defined by default but one can set it up via "tools"/"options"/"integrations" and specifying your desired hotkey, my coworkers all use: ctrl+shift+A on rare occasions I will highlight a keepass record and issue a "ctrl-v" which does a "push" of the autotype into the last active window. my...

I do not have the systems to reproduce but suggest trying to break problem into smaller units. * create a brand new .kdbx on each side with a stupid master password like a single lower case "a" * open up each side's .kdbx to prove all work. then close them. * copy each side's .kdbx over to the other side (do not overwrite) * open up all four .kdbx files then close them. you have just proven you can transfer a .kdbx from one side to the other and it still "works" if it hasn't worked make sure transfer...

I do not have the systems to reproduce but suggest trying to break problem into smaller units. * create a brand new .kdbx on each side with a stupid master password like a single lower case "a" * open up each side''s .kdbx to prove all work. then close them. * copy each side''s .kdbx over to the other side (do not overwrite) * open up all four .kdbx files then close them. you have just proven you can transfer a .kdbx from one side to the other and it still "works" if it hasn''t worked make sure transfer...

I do not have the systems to reproduce but suggest trying to break problem into smaller units. * create a brand new .kdbx on each side with a stupid master password like a single lower case "a" * open up each side''s .kdbx to prove all work. then close them. * copy each side''s .kdbx over to the other side (do not overwrite) * open up all four .kdbx files then close them. you have just proven you can transfer a .kdbx from one side to the other and it still "works" if it hasn''t worked make sure transfer...

I do not have the systems to reproduce but suggest trying to break problem into smaller units. * create a brand new .kdbx on each side with a stupid master password like a single lower case "a" * open up each side's .kdbx to prove all work. then close them. * copy each side's .kdbx over to the other side (do not overwrite) * open up all four .kdbx files then close them. you have just proven you can transfer a .kdbx from one side to the other and it still "works" if it hasn't worked make sure transfer...

it might be best/easiest if every workstation had local copy of the department .kdbx as well as every workstation using the pluggin "onedrivesync" to keep the one drive "master" current. let the pluggin automatically handle the file locking issues. basically the pluggin will perform a 2way recored level sync: - any time a user opens their local .kdbx - any time a user unlocks their .kdbx - anytime a user makes a change to a .kdbx record and saves. I would be inclined for staff to have a personal...

* try going into /tools/generate_password/advanced set both checkboxes and also data entry the characters ij what the above does is force keepasss to - make characters within a password string unique - exclude characters which on certain fonts/sizes commonly "look alike" such as lower case "l" and number "1" or uppercase "O" and number "0" - exclude other characters you might have trouble differentiating for my eyes, lower case "i" and "j" can look the same * also consider creating a custom mask...

* try going into /tools/generate_password/advanced set both checkboxes and also data entry the characters ij what the above does is force keepasss to - make characters within a password string unique - exclude characters which on certain fonts/sizes commonly "look alike" such as lower case "l" and number "1" or uppercase "O" and number "0" - exclude other characters you might have trouble differentiating for my eyes, lower case "i" and "j" can look the same * also consider creating a custom mask...