Sworddragon

I'm very well aware of the threat from compromised upstream/downstream sources as well of some recent cases like some games on Steam. But those have nothing to do with the feature requested here as apparently almost everybody is still wrongly assuming I'm requesting a feature to enable automatic updates. But let's just go with your case and assume the KeePass repository would be compromised. Even in such a case the feature discussed here would not help infecting computer systems more than the current...

I see, but what is the main issue here? The main change that is needed is that the installer supports silent installations if it doesn't already, which effectively pre-selects the last settings the user choosed within it (which it already does) and simply continues while not being visible. That might be even useful as a feature request on its own. Other than that the main complexity comes from handling the network logic and handling the migration of the new installation but those are not too much...

I see, but what is the main issue here? The main change that is needed is that the installer supports silent installations if it doesn't already, which effectively pre-selects the last settings the user choosed within it (which it already does) and simply continues while not being visible. That might be even useful as a feature request on its own. Other than that the main complexity comes from handling the network logic and handling the migration of the new installation but those are not too much...

But your first paragraph does not apply here since the user always authorizes this action before a new version of KeePass is even downloaded. It would only be true if we would talk about true automatic updates (e.g. KeePass would do the checking, downloading and installing of updates periodically without user interaction) and not improving installing updates manually what this ticket requests. And while your second paragraph is true in general it involves an issue (if we ignore the extra work): More...

I see, but what is the main issue here? The main change that is needed is that the installer supports silent installations if it doesn't already, which effectively pre-selects the last settings the user choosed within it (which it already does) and simply continues while not being visible. That might be even useful as a feature request on its own. Other than that the main complexity comes from handling the network logic and handling the migration of the new installation on the cleaning up process...

There are already such feature requests? I have even searched before creating this one but the only ones I found were about automatic updates. And even Paul does wrongly assume I'm talking about automatic updates. But this ticket requests an improvement for doing explicit user-initiated manual updates which is a big difference. Unless there are indeed already such feature requests but then I have to complain to Google for not finding them (but their search engine isn't really good anymore) and even...

There are already such feature requests? I have even searched before creating this one but the only ones I found were about automatic updates. And even Paul does wrongly assume I'm talking about automatic updates. But this ticket requests an improvement for doing explicit user-initiated manual updates which is a big difference. Unless there are indeed feature requests but then I have to complain to Google for not finding them (but their search engine isn't really good anymore) and even more to SourceForge...

There are already such feature requests? I have even searched before creating this one but the only ones I found were about automatic updates. And even Paul does wrongly assume I'm talking about automatic updates. But this ticket requests an improvement for doing explicit user-initiated manual updates which is a big difference. Unless there are indeed feature requests but then I have to complain to Google for not finding them (but their search engine isn't really good anymore) and even more to Sourceforge...