KeePass 2.61.1 (both setup and zip file) is listed as "No security vendors flagged this file as malicious" on Virus Total (https://www.virustotal.com/gui/home/upload). Make sure that you have downloaded KeePass via the official download site accessed via https://keepass.info/download.html. To confirm that you have downloaded authentic KeePass files, check the file hash of the download, e.g. SHA26, against the published file hashes obtained from the KeePass website at https://keepass.info/integrity.html....
I went to install 2.61.1, needing to use administrator access request on a university computer. The install was blocked and noted as malware. I did not have any issues on previous versions installed on the same PC. 2.60 is installed and working without issue. Any ideas on why this is being identified as malware?
No. It's a plug-in that intereacts with Windows only and KeePass works with other OSes. cheers, Paul
Does this Passkey will come natively in the KeePass?
Did you see Also include the following characters: in the generator?
Using the database locally and allowing Dropbox to sync that file is likely to cause data loss because Dropbox doesn't know anything about the internal data and just copies the latest files over the top. You need to keep a second copy of the database and use that as the local file. Then use KeePass to sync to the file that Dropbox copies to the cloud. See the full description here. https://keepass.info/help/kb/trigger_examples.html#dbsync cheers, Paul
HI Paul I have a Dropbox folder with 350 subfolders of things, like my passwords, which I want to save to The Cloud and also have available on a couple of other machines. A total of 6GB. Unfortunately Dropbox decided, unilaterally, that the default was " only available online" which probably suits small phones. But with several terabytes of space on my desktop I want a physical copy there, in case Dropbox or my broadband should go down. I will keep an eye on it and if any other programs have problems...
Reference: https://github.com/Rookiestyle/KeePassOTP/issues/188
Deleted database's plugin data entries are restored after sync
The KeePass write mechanism is designed to prevent errors on media that is not 100%. Writing to an internal disk is not an issue so it is OK to turn the transactions off, but make sure you keep regular backups (which you should do anyway). I would be working out what is going on because it may have other repercussions. Your description suggest you have setup Dropbox to take over your entire disk, instead of just syncing some of your documents. What documents / folders did you setup in Dropbox? cheers,...
Thanks for the quick response Paul. Turning off transactions, both config and main database solved problem , turning off either one is no good. What is the downside of doing this? Does it increase risk of corruption if machine shuts down during write? Keepass recently asked to update to the latest version. While fault finding I have uninstalled KP and reinstalled latest version 2.61.1 Dropbox changed everything to "Only available on line" but I switched it back to "always available". I have checked...
Appdata\roaming\keepass should only be written to by KeePass, but it seems something else is interfering. When KeePass is closed, or a configuration item is changed, the config file is rewritten. KeePass uses transactions to write files and you can turn them off to test your system. Tools > Options > Advanced. Scroll down to File Input/Output Connections Turn off Use file transactions for writing configuration settings. If this fixes it you need to work out what is preventing KeePass writing to the...
Hi, I have been a happy Keepass uses for several years, sharing a single file between my Windows 10 64bit desktop and my Android phone with DropBox. Recently when I try to start Keepass (2.61) on the PC I get: "Configuration error, Failed to load the specified file. Root element is missing". Investigation reveals the config.xml file in Appdata\roaming\keepass is a 0 byte file. If I delete it Keepass recreates the correct 4k file, but next time I start it has changed it back to 0 bytes. The backup...
Thanks for clarification. I'll ask them there.
KeePassXC is here. cheers, Paul
KeePass and KeePassXC are different projects. Best regards, Dominik
voleg@noname:~ $ ll $(find .cache .config -type f | grep -i keepas) -rw-r--r-- 1 voleg voleg 2033 Jun 17 20:15 .cache/keepassxc/keepassxc.ini -rw------- 1 voleg voleg 155 Feb 22 12:48 .config/KeePassXCrc -rw-r--r-- 1 voleg voleg 369 Feb 1 18:43 .config/autostart/org.keepassxc.KeePassXC.desktop -rw-r--r-- 1 voleg voleg 4026 Jun 11 11:26 .config/keepassxc/keepassxc.ini Exactly .cache/keepassxc/keepassxc.ini set starting behaviour, last open database and window sizing.
Hi Dominik I have tested the "KeePass_260616" version a bit, and as far as I can see it works just fine - i.e. clears the latest search argument when locking the databases or closing one or more open databases. Thank you for your very quick response and handling of this !!! :-) Best regards Frank
On Linux systems, the local configuration file is typically stored in '$XDG_CONFIG_HOME/KeePass' (which often is '~/.config/KeePass'). Best regards, Dominik
My ~/.cache is tmpfs and keepass lost its configuration every restart. Is it possible to use ~/.config directory as any other tools use ?
I've now added code such that the search term in the 'Find' dialog is now cleared when closing a database. This can be disabled using the UIFlags bit 0x100000 (up to now, this bit applied only to the quick search terms, now it applies also to the search term in the 'Find' dialog). Here's the latest development snapshot for testing: https://keepass.info/filepool/KeePass_260616.zip Thanks and best regards, Dominik
In reviewing my initial response I see that I confirmed the apparent behavior of your proposed workaround, but asserted that your analysis of the behavior was incorrect. Your subsequent post added details that would require additional off-topic discussion and verification. I don't see any reason to alter my conclusion that your post was going to require a lot of off-topic discussion and investigation that would be better accomplished in an independent thread.
My posts have been focused on KeePass behavior, Auto-Type, and practical ways to stop an unwanted Auto-Type sequence. The original poster specifically complained that once Auto-Type starts, there can be a "point of no return" where the user cannot stop it before data is submitted. I described a method that I have been using and testing for approximately one year. During that time, it has consistently worked for me as a practical way to stop an unwanted Auto-Type sequence by activating KeePass, either...
Hi I'm not sure if this has been this way always (but I don't think so), but if I search in Keepass (2.6.1 (x64)) via CTRL+F Keepass remembers the search argument even when I lock or close all open databases. If some evil person with access to my PC and Windows session now creates a new database or opens an existing one who he has access to (while mine still is locked/closed) and that person then initiates a search via CTRL+F this person can see my latest search argument - which of course might contain...
Describing a functional workaround to the original poster's problem would be an on-topic post, but that is not what your posts are doing. You are hijcking this post by asking for help about an approach for a workaround that you think might offer a solution. Your help topic will extended this thread with unrelated help related discussion like what you just posted and that am responding to this one time. This peripheral help discussion dilutes the topic and makes the on-topic discussion difficult to...
Describing a functional workaround to the original poster's problem would be an on-topic post, but that is not what your posts are doing. You are hijcking this post by asking for help about an approach for a workaround that you think might offer a solution. Your help topic will extended this thread with unrelated help related discussion like what what you just posted and that am responding to this one time. This peripheral help discussion dilutes the topic and makes the on-topic discussion difficult...
Describing a functional workaround to the original poster's problem would be an on-topic post, but that is not what your posts are doing. You are hijcking this post by asking for help an a approach for a workaround that you think might offer a solution. Your help topic will extended this thread with unrelated help related discussion like what what you just posted and that am responding to this one time. This peripheral help discussion dilutes the topic and makes the on-topic discussion difficult...
Describing a functional workaround to the original poster's problem would be an on topic post, but that is not what your posts are doing. You are hijcking this post by asking for help an a approach for a workaround that you think might offer a solution. Your help topic will extended this thread with unrelated help related discussion like what what you just posted and that am responding to this one time. This peripheral help discussion dilutes the topic and makes the on-topic discussion difficult...
Describing a functional workaround to the original poster's problem would be an on topic post, but that is not what your posts are doing. You are hijcking this post by asking for help an a approach for a workaround that you think might offer a solution. Your help topic will extended this thread with unrelated help related discussion like what what you just posted and that am responding to this one time. This peripheral help discussion dilutes the topic and makes the on-topic discussion difficult...
Describing a functional workaround to the original poster's problem would be an on topic post, but that is not what your posts are doing. You are hijcking this post by asking for help an a approach for a workaround that you think might offer a solution. Your help topic will extended this thread with unrelated help related discussion like what what you just posted and that am responding to this one time. This peripheral help discussion dilutes the topic and makes the on-topic discussion difficult...
I respectfully disagree with the suggestion that my post was unrelated to the original topic. My post directly relates to the thread title: Auto-Type on by default is dangerous" My post also directly relates to the original poster's concern: "point of no return: When you paste something by accident, the text sits in the input field. You can see it and delete it. By contrast, KeePass’s default Auto-Type sequence ends with an {ENTER} command. The machine physically executes the submission before a...
I respectfully disagree with the suggestion that my post was unrelated to the original topic. My post directly relates to the thread title: Auto-Type on by default is dangerous" My post also directly relates to the original poster's concern: "point of no return: When you paste something by accident, the text sits in the input field. You can see it and delete it. By contrast, KeePass’s default Auto-Type sequence ends with an {ENTER} command. The machine physically executes the submission before a...
What you are observing is the result of moving the focus out of a field while KeePass is auto-typing. In your case you are moving the focus to an object (KeePass shortcut) that has very limited ability to receive keystroke input. It is similar to typing into an empty spot on the Windows desktop, nothing happens. The desktop is waiting for specialized input, e.g. mouse clicks and modifier key input, everything else is ignored. <window>* - KeePass<window> is not a valid target filter, it has no effect...
What you are observing is the result of moving the focus out of a field while KeePass is auto-typing. In your case you are moving the focus to an object (KeePass shortcut) that has very limited ability to receive keystroke input. It is similar to typing into an empty spot on the Windows desktop, nothing happens. The desktop waiting for for specialized input, e.g. mouse clicks and modifier key input, everything else is thrown away. <window>* - KeePass<window> is not a valid target filter, it has no...
What you are observing is the result of moving the focus out of a field while KeePass is auto-typing. In your case you are moving the focus to an object (KeePass shortcut) that has very limited ability to receive keystroke input. It is similar to typing into an empty spot on the Windows desktop, nothing happens. The desktop is looking for specialized input, e.g. mouse clicks and modifier key input. <window>* - KeePass<window> is not a valid target filter, it has no effect in any context. In the future...
What you are observing is the result of moving the focus out of a field while KeePass is auto-typing. In your case you are moving the focus to an object (KeePass shortcut) that has very limited ability to receive keystroke input. It is similar to typing into an empty spot on the Windows desktop, nothing happens. The desktop is looking for specialize input, e.g. mouse clicks and modifier key input. <window>* - KeePass<window> is not a valid target filter, it has no effect in any context. In the future...
What you are observing is the result of moving the focus out of a field while KeePass is auto-typing. In your case you are moving the focus to an object (KeePass shortcut) that has very limited ability to receive keystroke input. It is similar to typing into an empty spot on the Windows desktop, nothing happens. <window>* - KeePass<window> is not a valid target filter, it has no effect in any context. In the future please don't post into existing threads unless you are making a direct contribution...
What you are observing is the result of moving the focus out of a field while KeePass auto-typing. In your case you are moving the focus to an object (KeePass shortcut) that has very limited ability to receive keystroke input. It is similar to typing into an empty spot on the Windows desktop, nothing happens. <window>* - KeePass<window> is not a valid target filter, it has no effect in any context. In the future please don't post into existing threads unless you are making a direct contribution regarding...
KeePass upgraded the database format to KDBX 4.0 in KeePass 2.35. KeePass is backward compatible with old database formats but the opposite is not true. See https://keepass.info/help/kb/kdbx_4.html for a description of the migration path and the factors that require an automatic database update. In general you should plan an expeditious update of all your KeePass installations. Whether you need to update all installations at once depends on whether a failure for an old version of KeePass to open...
Can I assume then that the format of the KeePass data file (.kdbx) hasn't change or is it that the format has change but the latest version of KeePass can read the old format files? Thanks for the help BTW.
You will need to upgrade each KeePass installation individually. To avoid unexpected issues use the KeePass install file that is appropriate appropriate for each installation, i.e. KeePass-2.61.1-Setup.exe for installed copies, and KeePass-2.61.1.zip for portable copies. See below: If are using the installed KeePass version (verify using Setup>Apps>Installed Apps or Control Panel>Programs>Programs and Features) use KeePass-2.61.1-Setup.exe to update the installation. For all portable copies use KeePass-2.61.1.zip....
You will need to upgrade each KeePass installation individually. To avoid unexpected issues use the KeePass install file that is appropriate appropriate for each installation, i.e. KeePass-2.61.1-Setup.exe for installed copies, and KeePass-2.61.1.zip for portable copies. See below: If are using the installed KeePass version (verify using Setup>Apps>Installed Apps or Control Panel>Programs>Programs and Features) use KeePass-2.61.1-Setup.exe to update the installation. For all portable copies use KeePass-2.61.1.zip....
When I add the following entry to the KeePass 2.61 XML configuration file: <autotypeabortonwindows> <window>* - KeePass</window> </autotypeabortonwindows> Auto-Type is aborted whenever the KeePass window becomes active. For example, if I click the KeePass icon on the taskbar while Auto-Type is running, KeePass is activated and the Auto-Type process stops immediately. I am using this as a way to stop an unwanted Auto-Type sequence quickly by activating KeePass. However, I would like to know whether...
I've been running KeePass for many years without upgrading. I'm running version 2.25. I have a copy of this on several PCs and many USB sticks. Can I simply install the latest version (2.61.1 at the moment) and point it at my existing KeePass .kdbx file and everything will work or do I have to go through some data conversion process?
I use KP2A and open a database from a webdav server on the internet. KP2A caches a copy of that database and will sync changes to the webdav server. On my PC KeePass is set up to sync my local database to the webdav server on save. I am effectively using 3 database files, 2 local ones and a master in the cloud that I sync with. This is described in the KeePass trigger examples. cheers, Paul
The KeePass ZIP file does not contain a config file. You can create one before starting KeePass or it will create one when it closes (or if you change a setting). If you do not have an existing user config file, KeePass will use the global file by default. If you already have a user config file, KeePass will use that by default. cheers, Paul
I totally agree Abdul. Alternative programs like KeePassXc don't impress me when it comes to their overall security architecture and program design. Perhaps by 2026 it will be time to introduce some visual improvements.
To clarify, Keepass2Android Password Safe 1.14-r4 is not KeePass. It is a third party app that is file compatible with KeePass databases. I used KeePass2Android a number of years ago when I had an Android Phone. I don't remember it having a "synchronize" button but the current documentation (see below) does mention the ability to merge changes. I suggest you read the documentation for KeePass2Android and pay special attention to the section on "Opening an existing database". There are two bullet...
To clarify, Keepass2Android Password Safe 1.14-r4 is not KeePass. It is a third party app that is file compatible with KeePass databases. I used KeePass2Android a number of years ago when I had an Android Phone. I don't remember it having a "synchronize" button but the current documentation (see below) does mention the ability to merge changes. I suggest you read the documentation for KeePass2Android and pay special attention to the section on "Opening an existing database". There are two bullet...
To clarify, Keepass2Android Password Safe 1.14-r4 is not KeePass. It is a third party app that is file compatible with KeePass databases. I used KeePass2Android a number of years ago when I had an Android Phone. I don't remember it having a "synchronize" button but the current documentation (see below) does mention the ability to merge changes. I suggest you read the documentation for KeePass2Android and pay special attention to the section on "Opening an existing database". There are two bullet...
To clarify, Keepass2Android Password Safe 1.14-r4 is not KeePass. It is a third party app that is file compatible with KeePass databases. I used KeePass2Android a number of years ago when I had an Android Phone. I don't remember it having a "synchronize" button but the current documentation (see below) does mention the ability to merge changes. I suggest you read the documentation for KeePass2Android and pay special attention to the section on "Opening an existing database". There are two bullet...
To clarify, Keepass2Android Password Safe 1.14-r4 is not KeePass. It is a third party app that is file compatible with KeePass databases. I used KeePass2Android a number of years ago when I had an Android Phone. I don't remember it having a "synchronize" button but the current documentation (see below) does mention the ability to merge changes. I suggest you read the documentation for KeePass2Android and pay special attention to the section on "Opening an existing database". There are two bullet...
To clarify, Keepass2Android Password Safe 1.14-r4 is not KeePass. It is a third party app that is file compatible with KeePass databases. I used KeePass2Android a number of years ago when I had an Android Phone but I don't remember it having a "synchronize" button but the current documentation (see below) does mention the ability to merge changes. There was a process for opening a database saved on a shared cloud service such as OneDrive, GoogleDrive or DropBox. I suggest you read the documentation...
To clarify, Keepass2Android Password Safe 1.14-r4 is not KeePass. It is a third party app that is file compatible with KeePass databases. I used KeePass2Android a number of years ago when I had an Android Phone but I don't remember it having a "synchronize" button. There was a process for opening a database saved on a shared cloud service such as OneDrive, GoogleDrive or DropBox. I suggest you read the documentation for KeePass2Android and pay special attention to the section on "Opening an existing...
Yes, in the android app.
Hi wellread, thanks for your advice. In the App I use "synchronize database. But when I checked recently items I had changed, those for not to be found on my mobile after synchronising the database.
Sorry, a bit late. Version 1.14-r4
My PreferUserConfiguration is set to False. Since I didn't mess with that, I assume that the portable version has that setting by default.
Yes this function needs overhaul as the fonts in new system is too small for older people to see, it should be updated
That depends on what the user config setting is in the global config file (PreferUserConfiguration). What is yours set to? cheers, Paul
The answer is that I am using the portable version and the documentations says: "If you downloaded the portable version of KeePass (ZIP package), KeePass will try to store its configuration in the application directory. No configuration settings will be stored in the user directory (if the global configuration file is writable)."
KeePass should use a user config, $XDG_CONFIG_HOME/KeePass, unless you set it to use the global one (see the bottom of the config help page). cheers, Paul
The issue is corrected. I think it all relates to the fact that when I update KeePass, I just download it to my Downloads folder and update my link to "keepass2" to point at the latest download. So, in that situation, KeePass uses the config file in that same folder. Copied my previous config file to that latest downloaded folder and all is working as it should.
Interesting, but that's not what I'm looking for. The plugin lets you increase the font size of the menu, but it doesn't scale all elements. The link to the FAQ about adjusting Windows scaling isn't exactly what I'm looking for. There must be a way to scale everything (menu, tree structure entries, entries, menu, program size, etc.) based on a set value. I’m just not sure if the icons would become “blurry” since they might not be available in higher resolution. Instead of another plugin, it would...
TOTP generation looks good but fails secretly
The KeeUIExt plugin provides an option for that: https://keepass.info/plugins.html#keeuiext Best regards, Dominik
Global auto-type is a documented feature of KeePass, it is not unexpected behavior if a user installed KeePass. Also it appears that you have been aware of this behavior for 1 or 2 years. You can hardly claim surprise. Correct, in general KeePass auto-type is more secure than copy/paste. Ignorance of how a major product feature works is not an adequate excuse for using the feature incorrectly. Turning a serious idea like Secure by Default into a platitude so that it can apply to protecting a user...
Global auto-type is a documented feature of KeePass, it is not unexpected behavior if a user installed KeePass. Also it appears that you have been aware of this behavior for at least 2 years. You can hardly claim surprise. Correct, in general KeePass auto-type is more secure than copy/paste. Ignorance of how a major product feature works is not an adequate excuse for using the feature incorrectly. Turning a serious idea like Secure by Default into a platitude so that it can apply to protecting a...
Global auto-type is a documented feature of KeePass, it is not unexpected behavior if a user installed KeePass. Also it appears that you have been aware of this behavior for at least 2 years. You can hardly claim surprise. Correct, in general KeePass auto-type is more secure than copy/paste. Ignorance of how a major product feature works is not an adequate excuse for using the feature incorrectly. Turning a serious idea like Secure by Default into a platitude so that it can apply to protecting a...
Hello, I've been using KeePass for a very long time, and there's one thing that's been bothering me for ages. I find the size of the KeePass window—and all the associated buttons, elements, text, etc.—somehow “too small.” Okay, I have a 4K monitor, but I've already set an optimal scaling of 150% for everything else. If I set it to 175%, I’d lose a ton of space for everything else. I’ve already increased the font size in KeePass, but that only affects the text and not other elements, which eventually...
Hello, I've been using KeePass for a very long time, and there's one thing that's been bothering me for ages. I find the size of the KeePass window—and all the associated buttons, elements, text, etc.—somehow “too small.” Okay, I have a 4K monitor, but I've already set an optimal scaling of 150% for everything else. If I set it to 175%, I’d lose a ton of space for everything else. I’ve already increased the font size in KeePass, but that only affects the text and not other elements, which eventually...
Hello, I've been using KeePass for a very long time, and there's one thing that's been bothering me for ages. I find the size of the KeePass window—and all the associated buttons, elements, text, etc.—somehow “too small.” Okay, I have a 4K monitor, but I've already set an optimal scaling of 150% for everything else. If I set it to 175%, I’d lose a ton of space for everything else. I’ve already increased the font size in KeePass, but that only affects the text and not other elements, which eventually...
Comparing Global Auto Type to be just a slightly more advanced version of paste is a bad comparison here, because the differences are precisely what makes one of them considered insecure: point of no return: When you paste something by accident, the text sits in the input field. You can see it and delete it. By contrast, KeePass’s default Auto-Type sequence ends with an {ENTER} command. The machine physically executes the submission before a shocked human can abort it. Universal Standard vs unexpected...
KeePass stores the path relative to KeePass.exe, unless that path is on a different drive. The details are stored in the KeePass config file, under <Application><LastUsedFile> and <MostRecentlyUsed>. cheers, Paul
KeePass stores the path relative to KeePass.exe, unless that path is on a different drive. The details are stored in the KeePass config file, under <application><lastusedfile> and <mostrecentlyused>.</mostrecentlyused></lastusedfile></application> cheers, Paul
Try clearing the "Recent Files" list, to see if KeePass will rebuild the list correctly Otherwise, KeePass is native Windows program where "Recent Files" list works fine. Since KeePass requires mono to run on Linux a likely source of the issue is mono. Make sure you are using the current version of mono.
I am running Keepass version 2.61.1 on my Ubuntu 12 laptop. If I want to synchronize my open database with a database that is on a network mounted drive (as I normally do), that drive is not correctly listed in the "Recent Files" list. The path to the network mounted drive appears in the list, but the path to my home folder is prepended to it, creating a non-existent path. Is this a bug? Or is there a setting that I need to set?
Global Auto Type is little more than an slightly more advanced version of paste with the added protection that it validates the window title before it types, and by default eschews the clipboard. By your standard, paste is a catastrophic error waiting to happen and all software should be shipped with paste and the clipboard disabled by default because it is possible for a user to paste something sensitive in the wrong place.
It isn't necessary to cripple a product out of the box because a user might make an easily correctable mistake. With due Respect Your viewpoint is about 2 decades behind current software engineering standards. In modern cybersecurity, if a system allows a user to accidentally trigger a catastrophic error by default, that is a design failure, not a user failure. The standard is and has been for many years now "Secure by Default. Risky by opt-in". Nowadays, everyone expects actively maintained software...
You know what they say - different folks, different workflows.. Exactly. Workflows are different to everyone. And having a globally active hotkey on every single user by default to support specific workflows is the exact opposite of respecting different workflows. Would a single checkbox on install really destroy your whole workflow? I doubt it. Will it remove a security risk to everyone who doesnt use GAT? Yes for sure it would!! AT and GAT are one, or two, of the features that originally attracted...
That sounds right! Updating the .dll and the MSIX is the whole process, so your install is now fully on v1.1.1. If you'd like to double-check, you can open the provider app and confirm the status there.
I have downloaded the v 1.1.1 and updated the .dll and also the MSIX as well, so this is complete right?
Thanks for response, really appreciated, will download from github
It's manual: you grab the new release, install the provider MSIX package and copy the plugin into your KeePass installation, same as the first install. There's no auto-update, which is how nearly all KeePass plugins work, and honestly I think that's the right call for security reasons. I see KeePass as an offline-first application, and any feature with internet access, like auto-update, might introduce new attack vectors.
does passkey plugins update automatically or need to download new release and update manually?
AT and GAT are one, or two, of the features that originally attracted me to KeePass. Not only is KP my password manager, it is also a kind of a bookmarks manager. I refer to it that way due only to the fact that there are several websites that I will only access by going to them via the URL in KP. Auto Type comes in handy after that, and GAT is useful to me when a site is gotten to other means. I will agree that what's good for one person might not be so good for another. You know what they say -...
AT and GAT are one, or two, of the features that originally attracted me to KeePass. Not only is KP my password manager, it is also a kind of a bookmarks manager. I refer to it that way due only to the fact that there are several websites that I will only access by going to them via the URL in KP. Auto Type comes in handy after that, and GAT is useful to me when a site is gotten to other means. I will agree that what's good for one person might not be so good for another. You know what they say -...
KeePass has certain capabilities and features. Familiarizing oneself with the feature set of a product after installing it on your device is prudent behavior. Making assumptions about how a product feature works, and failure to familiarize oneself with the documentation are user mistakes. It isn't necessary to cripple a product out of the box because a user might make an easily correctable mistake.
I disagree on what is considered a key feature here. I havent heard about Global auto type and I used keepass for like 5 years now... The key feature of keepass in my eyes is being a password manager, ie a programm to enter and restore passowords from. everything else is while being super useful more of a quality of life improvement, especially global auto type since it is literally just a shortcut for alt tabbing to keepass, strg f the website, and strg v the result.... I dont argue that global...
I agree to disagree on what is considered a key feature here. I havent heard about Global auto type and I used keepass for like 5 years now... The key feature of keepass in my eyes is being a password manager, ie a programm to enter and restore passowords from. everything else is while being super useful more of a quality of life improvement, especially global auto type since it is literally just a shortcut for alt tabbing to keepass, strg f the website, and strg v the result.... I dont argue that...
I agree to disagree on what is considered a key feature here. I havent heard about Global auto type and I used keepass for like 5 years now... The key feature of keepass in my eyes is being a password manager, ie a programm to enter and restore passowords from. everything else is while being super useful more of a quality of life improvement, especially global auto type since it is literally just a shortcut for alt tabbing to keepass, strg f the website, and strg v the result.... I dont argue that...
Thats my main criticism! There never was a "before"!!! I never explicitly enabled that feature. I didnt even know that global auto-type existed!!! How should I understand a feature I dont know about. It should just be disabled on default!! GAT might be mentioned somewhere in the docs, and to disable by default a key feature of a program would be absolutely ridiculous.
no, I do understand the feature now and it wont happen for me again. I dont need help for myself I just wanna point out the currently existing flaw.... But here you said something interesting Every KeePass user should understand how this basic KeePass functionality works before they start using global auto-type. Thats my main criticism! There never was a "before"!!! I never explicitly enabled that feature. I didnt even know that global auto-type existed!!! How should I understand a feature I dont...