(I have a convenience script for the Firefox extension, see. If there was an update, then either the checksums would fail, or I would change the _amo_file ID in order to download the new version of the Firefox extension. I have just double-checked and none of the (unversioned) source files have been updated, so this package should still be valid. (But then again, the release notes say the latest Chrome webstore version is 4.1.55 and the latest Firefox version is 4.1.53 and apparently neither are true.)

The opera plugin is installed, again as per the official installer script, from the unversioned CRX hosted on their website, which does have a libnplastpass.so and is also behind the Chrome webstore version - I have no idea why. The native messaging binary is installed, as per the official Lastpass universal installer, from their universal installer tarball (and the webstore doesn't contain libnplastpass.so at all). but that is a no-op at the moment as well.Īdditionally, the chrome browser extension is downloaded and updated by Chrome itself, since Chrome doesn't do locally-installed global extensions like Firefox does - all that this package does is install a policy file telling Chrome to install lastpass on its own. If the files were updated on the Lastpass server, then it would redownload the same *unversioned* URLs under an updated local name, and update the checksums if relevant. The pkgver is not actually used in the download urls at all, so changing the pkgver and the _chromever accomplishes nothing other than giving the source files a unique local name.

Last pass chrome download