With all these updates to the plugin, can we somehow auto-update?

[shackrock]

Not that I don't appreciate all the hard work and new feature updates... =) ...but with all these updates every few days, can we somehow get an auto-update feature with it? =)

I guess this is a feature request more than an "issue" - sorry if it's posted in the wrong place.

[lsgd]

Unfortunately it's not possible to replace the plugin file while KeePass is running. Therefor I cannot implement an update routine which runs in the plugin. I have to start a second process which checks whether KeePass has been closed, starts the download, replaces the file and restarts KeePass. But that's not a good solution.

You can set the update-check-interval in chromeIPass from 3 days to 1 week or 1 month.

But currently there are no more feature requests from users and no known bugs. Therefor I think from now on there will be longer version-cycles then in the last two months.

[pfn]

I've been wanting to implement the KeePass version check feature, but haven't gotten around to it. It won't be an auto-update, but it will at least prompt on a more frequent basis (in addition to chromeipass prompting).

http://keepass.info/help/v2_dev/plg_index.html#upd

On Fri, Apr 12, 2013 at 2:37 PM, Lukas Schulze notifications@github.comwrote:

Unfortunately it's not possible to replace the plugin file while KeePass is running. Therefor I cannot implement an update routine which runs in the plugin. I have to start a second process which checks whether KeePass has been closed, starts the download, replaces the file and restarts KeePass. But that's not a good solution.

You can set the update-check-interval in chromeIPass from 3 days to 1 week or 1 month.

But currently there are no more feature requests from users and no known bugs. Therefor I think from now on there will be longer version-cycles then in the last two months.

— Reply to this email directly or view it on GitHubhttps://github.com/pfn/keepasshttp/issues/106#issuecomment-16319070 .

[lsgd]

This feature is already implemented. It checks the file update-version.txt for new versions.

[pfn]

Oh, well then, thanks for doing that, heh.

Yeah, auto-update isn't necessary, IMO, there's been a spate of updates recently, but that should die down. Maybe when the next flurry of updates comes in when I start to think about how to better harden up the data-exchange protocol (a user has pointed out several flaws that could potentially cause data corruption and expose some characteristics of user passwords)

On Fri, Apr 12, 2013 at 3:30 PM, Lukas Schulze notifications@github.comwrote:

This feature is already implemented.

— Reply to this email directly or view it on GitHubhttps://github.com/pfn/keepasshttp/issues/106#issuecomment-16321026 .

[prashker]

I seem to be able to manually replace the PLGX while Keepass is running. It won't load the new version until restart, but still that is better than having to manually do it.

That leads me to believe that the PLGX is loaded in once, and retained in memory (as there are no locks on the file itself)...could you not have an update routine that replaces the file, making it use the new version on restart of keepass?

Similar to how Google Chrome updates, it replaces the files, but only loads them the next time you restart the browser.

Or am I missing something?

[tastyratz]

Old request but still valid. I have the hibp plugin which seems to get updated frequently. If there was a direct download, way to update from within keepass, it would certainly be convenient.

Understanding that plugins are only activated on next startup is perfectly reasonable since they can be replaced anyways while keepass is running.

I see the value in an update downloader to keepass.