Macpass update install#
Macpass update update#
Macpass update password#
Macpass update plus#

It would also make locking much faster (now, there's a slight delay because the document is always saved).ītw, there is something wrong in the way MacPass (0.6.2) displays a document status in the top-left close button. I do not see how that could result in data loss: you simply need to close the document's view and wipe memory. I am not asking to avoid saving a document altogether when locking, but to avoid it when the document has not been modified at all since it was opened or last saved. This was different in previous releases of MacPass and resulted in data loss for a lot of users. I find that a bit counterintuitive and confusing, especially for an app that deals with privacy and security. But is it typical behaviour, or one recommended by Apple? Anyway, I haven't checked how TextEdit writes such a document, but MacPass writes a different file every time even if no change has been made (I mean, not only its attributes, such as the modified timestamp, are updated, but also its content, although not in an apparent way). If the user issues a save the file is written regardless of state. Keepass writes on lock, so it seemed appropriate to do the same.

Macpass update password#

By saving on lock the master password change is in effect directly after the lock (which still might never occur) Keepass With autosave this should be immediate but it might be postponed in certain scenarios. If the user changes the master key this change is not affective until the next save. Also, this is a good way to propagate updates to other clients if the file cannot be saved frequently via autosave mechanics of NSDocument. By saving on lock, the need for user interaction is removed. 0.6.2 does not have merge support, it only allows to decide for reload or overwrite on the event of an external change to the database. Merges cannot take place without unlocking the database and asking for merge strategies.

If the database is locked and changed in any way, changes should be merged. My reasoning for this behaviour: External changes Currently there's autosave in place so this issue should not arise anymore. I would suggest no change to that since it's a use based action. ℹ️About GitHub Wiki SEE, a search engine enabler for GitHub WikisĪs GitHub blocks most GitHub Wikis from search engines.If the user issues a save the file is written regardless of state. You do not need to use MacPass and can simply manage the files in the folder via the Finder. Installing simply moves the file into ~/Library/Application Support/MacPass/ and uninstalling deletes the file. Removing works by selecting the plugin and hitting the minus.

Macpass update plus#

mpplugin file onto the plugin list in the plugin preferences window or add it by clicking the plus button and selecting the file.

Macpass update install#

There are multiple ways to install a Plugin.

Macpass update update#

If you have plugins that are not compatible with the current version of MacPass, open the plugin browser and see if an update is available Adding and Removing Plugins This will load a list and allows you to see if anything is out of date or new plugins are available. Any errors while loading the plugins will be listed there.Īll plugins know to MacPass can be found by clicking on the Browse available Plugins… button in the preferences. A list of all plugins found by MacPass can be found there. MacPass offers an overview of plugins in the plugin preferences. Installed plugins can be found in ~/Library/Application Support/MacPass/.

Available plugins are listed in the Plugin Repository.

MacPass uses a Plugin-System to enable you to add custom functionality.