Package Details: lastpass

Git Clone URL: (read-only, click to copy)
Package Base: lastpass
Description: The Universal LastPass installer for Firefox, Chrome, and Opera
Upstream URL:
Licenses: custom
Submitter: Det
Maintainer: darose
Last Packager: darose
Votes: 96
Popularity: 0.169252
First Submitted: 2013-06-02 17:50 (UTC)
Last Updated: 2022-02-17 21:21 (UTC)

Latest Comments

darose commented on 2022-02-17 21:24 (UTC)

Alright I've experimentally adopted this package. I may have to drop it if it becomes too hard to maintain. I upgraded to v4.88.0.1. It looks working in both FF and Chromium, but LMK if anyone sees any issues.

darose commented on 2022-02-17 19:27 (UTC)

Oh wow. I've been using it without any issue for so long that I hadn't even realized that. If no one else wants to adopt it I can take a look and see if it's not too complicated to maintain.

duhbLow7 commented on 2022-02-17 18:22 (UTC)

This package is unmaintained and quite outdated.

eschwartz commented on 2020-09-09 00:31 (UTC) (edited on 2020-09-09 00:33 (UTC) by eschwartz)

Nice diff there for

-wget -O lpchrome_linux.crx ""
+wget -O lpchrome_linux.crx ",crx3&x=id%3Dhdokiejnpimakedhajhdlcegeplioahd%26uc"

What a waste of time this bump is. Grrr.

This file isn't even used by the package. I'm fixing this without bumping pkgrel, users who successfully built it in the past are unaffected.

daniel_shub commented on 2020-09-08 23:59 (UTC)

I am getting a build error for with makepkg in a clean chroot. The sha256 checksum of the lplinux-4.1.59.tar.bz2 file that gets downloaded (826e383a6bad905d942e22b14aee67dbc39e8f7a5243d706af787c8fcec6f158) does not match the checksum in the PKGBUILD. Looking at the downloaded lplinux-4.1.59.tar.bz2 file, while the version number has not changed with the updated lastpass/PKGBUILD, the tarball now contains a file with a date of 2020-08-31, which makes me think they may have changed something behind the scenes without incrementing the version number.

Det commented on 2019-07-11 11:51 (UTC)

He responses in complaining manners, but he's right.

eschwartz commented on 2019-04-03 17:17 (UTC) (edited on 2019-04-03 17:19 (UTC) by eschwartz)

No, it really isn't bad practice. It is bad practice to fail hard because you have a tightly interwoven dependency on makepkg internals (and the format that is absolutely, positively, guaranteedly documented, since I wrote the documentation). Given I have actually discussed this with one of the lead developers of yay, and my advice to not be vulnerable to breaking for any reason, was accepted, I consider myself justified in adding this.

I did not break yay. I discovered that yay was already broken. I also guaranteed that yay-git now supports upcoming versions of pacman.

Furthermore, the official policy of the AUR is that if an AUR helper does not work, you should use makepkg directly, and if makepkg itself does work, then the problem is automatically with the AUR helper and only the AUR helper.

I am not changing this, and it is not open for debate.

gromain commented on 2019-04-03 17:00 (UTC)

I think that adding an unreleased and undocumented feature to something is bad practice too, since it breaks tools that could not have been informed of coming changes.

thayne commented on 2019-04-01 06:49 (UTC)

Is b2sums supported by makepkg? I can't find any documentation on it.

linuxninja commented on 2019-04-01 02:18 (UTC)

Thanks for your quick response, and all of your hard work! Sometimes it's just not obvious how to prevent breaking changes, ey?

I will follow-up by reporting this issue via yay's reporting mechanism (github issues). I'll have to check the yay-git package to be sure it hasn't already been fixed, there, and maybe just a new release of yay is all that is needed.

eschwartz commented on 2019-04-01 02:04 (UTC) (edited on 2019-04-01 02:07 (UTC) by eschwartz)

Was this tested?

It was tested to work with makepkg, which is the gold standard...

I don't exactly test what every fad AUR helper does. Note that this sort of heuristic blacklisting of perfectly good packages means that yay would not work for packages that implement new features, immediately after makepkg itself received a new release. So I don't generally encourage this sort of error-checking anyway. It gives me flashbacks to pacaur and its "mismatched srcinfo" errors.

linuxninja commented on 2019-04-01 02:00 (UTC) (edited on 2019-04-01 02:00 (UTC) by linuxninja)

for the less informed who run into this issue, here's the quick and dirty on upgrading the aur package when yay breaks:

cd ~/.cache/yay/lastpass

makepkg -si

linuxninja commented on 2019-04-01 01:56 (UTC)

I'm also running into a breaking error with aur package upgrades:

yay error message:

:: Parsing SRCINFO (1/1): lastpass failed to parse lastpass: Line 30: Unknown key: "b2sums": b2sums = 493334b0cf11abe2add52a2935b1e3a4afdffd8b4b64d659913084257af058c51b2157fb1fdb4f78da9dee9f61750bcd0614661b092a66c6fd252eff35f348f8

This is a fatal error and aborts the entire yay run. I would suggest adding an as-yet unsupported line to the config is not backwards compatible for the various AUR tools. Maybe those tools should be given some time to either ignore invalid config lines, or add support for the new proposed config lines.

Was this tested? Can we remove the b2sums line until tools like yay have some time to get this added?

eyrie88 commented on 2019-03-31 22:07 (UTC)

Well, yay doesn't like it... :: Parsing SRCINFO (1/3): lastpass failed to parse lastpass: Line 30: Unknown key: "b2sums": b2sums = 493334b0cf11abe2add52a2935b1e3a4afdffd8b4b64d659913084257af058c51b2157fb1fdb4f78da9dee9f61750bcd0614661b092a66c6fd252eff35f348f8

eschwartz commented on 2019-03-31 21:05 (UTC) (edited on 2019-04-01 06:53 (UTC) by eschwartz)

I am indeed running an unreleased version of pacman/makepkg, and I'm also the one who added b2sums to pacman in git master (and the pacman-git package I maintain). :p

It's not a problem for old versions of makepkg, as old versions will ignore b2sums and rely exclusively on sha256sums (all you need is at least one valid algorithm) -- you won't get the advantage of collision resistance with multiple algorithms including an SHA-3 contender, but SHA-2 is still pretty good even without using two algorithms for redundancy.

Added: Whether an AUR helper (that I do not test) can correctly handle this does not bother me, since makepkg (the gold standard which I use to test) handles it just fine.

Jammie commented on 2019-03-31 21:00 (UTC)

Are you running an unreleased version of pacman/makepkg? I don't think b2sums is available yet.

awh commented on 2019-01-01 22:55 (UTC)

For some reason, with this package installed, when activating the copy password functionality in Firefox (about page said binary component is installed), it would hang my browser for multiple minutes, and not copy the password. After removing the package (about page said binary component is removed, but copy password still shows), the functionality behaves as normal.

coolpyrofreak commented on 2018-12-15 04:22 (UTC)

Looks like a new version was released on Dec. 13. Current version for Firefox is Chrome is at 4.21.0.

commented on 2018-12-10 09:43 (UTC)

Can this url set things back on track? It will install version in firefox. Seems to be the last... I rather have a working PKGBUILD of an old version than nothing at all.

eschwartz commented on 2018-12-05 16:57 (UTC)


That is /usr/lib/lastpass/nplastpass which is activated by /usr/lib/mozilla/native-messaging-hosts/com.lastpass.nplastpass.json I install both, and the specified functionality works fine on my computer.


Okay... Apparently version is simply gone from the Firefox addons site, but I have no clue why. I could revert the last commit, but I'd also need to add an epoch. I do have this file cached locally...

delusional commented on 2018-12-05 16:06 (UTC) is 404

SMOG commented on 2018-11-27 13:14 (UTC) and are actually needed also for Firefox. Without them, the ability of copying passwords to clipboard is not working on Firefox. It's not your fault of course because it's LastPass devs who are not providing those files as they should, but I just wanted to let you know.

more info about this problem can be found here:

eschwartz commented on 2018-09-02 02:50 (UTC)

Hmm, they just removed their own hosted copy in favor of downloading one from the Chrome webstore. Problem is, the only thing that crx is needed for, is the opera plugin, which is not contained in the chrome webstore version of the crx... which is logical because why was it ever there in the one hosted on

I'll note their linux download instructions and is therefore incorrect and not working.

I'm not really sure what the story is supposed to be here. But I don't use opera. So, I guess I will drop this, and use the new lplinux.tar.bz2 location for the chrome/firefox native messaging binary. Either that or someone who uses Opera can discuss with Lastpass support/tell me how to re-enable it.

Patricol commented on 2018-09-01 18:20 (UTC) is a 404 for me.

eschwartz commented on 2018-07-13 15:34 (UTC)

Yeah, I don't usually see extensions pulled like that. :/

Updated again.

I've been moving things to nvchecker so I should see updates faster anyway.

becatlibra commented on 2018-07-13 12:51 (UTC)

Currently getting a 404. It appears that 4.15.07 is no longer available

zman0900 commented on 2017-12-19 04:45 (UTC)

Binary component doesn't appear to be working with firefox. I tried deleting ~/.mozilla/firefox/<profile>/extensions/ just to be sure I am using the package provided extension, but the options to copy username or password are still missing. </profile>

In a windows VM using the same versions of firefox and the lastpass extension, installed with the lastpass provided universal installer, the copy options are there, so it seems like this should be working.

eschwartz commented on 2017-10-20 16:05 (UTC)

Oh, uh, whoops. [eschwartz@arch ~/git/pkgbuilds/lastpass]$ /usr/bin/diff -ur src/lastpass-4.2.0a pkg/lastpass/usr/lib/firefox/browser/extensions/ Binary files src/lastpass-4.2.0a/data/ and pkg/lastpass/usr/lib/firefox/browser/extensions/ differ So why did this all of a sudden start getting modified during tidy_strip? And I never noticed it when updating this, because my Firefox build has extension signing verification disabled. Try it now.

jskier commented on 2017-10-20 14:58 (UTC)

This version 4.2.0a-1 appears to have an unverified Firefox extension with it. I put in a support ticket and will follow up if necessary.

eschwartz commented on 2017-08-13 03:20 (UTC)

Whoops, I seem to have forgotten to add that when I switched the packaging logic to what I use in my other Firefox extensions. Fixed now.

nocturnus commented on 2017-08-13 03:09 (UTC)

'unzip' from the Extra Repository should be a dependency of the package, otherwise it will fail to build, due to unzip command usage.

eschwartz commented on 2017-07-17 23:44 (UTC) (edited on 2017-07-17 23:46 (UTC) by eschwartz)

I doubt it... 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. So your suggestion is a no-op. 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... but that is a no-op at the moment as well. Additionally, 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. The native messaging binary is installed, as per the official Lastpass universal installer, from their universal installer tarball (and the webstore doesn't contain at all). The opera plugin is installed, again as per the official installer script, from the unversioned CRX hosted on their website, which does have a and is also behind the Chrome webstore version -- I have no idea why. (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.) I have just double-checked and none of the (unversioned) source files have been updated, so this package should still be valid. 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 a convenience script for the Firefox extension, see ./ ... So given that nothing which you described should have fixed anything, I am not sure what the problem is or how you expect me to fix it. Maybe restarting Chrome caused it to fix itself?

bsdfirst commented on 2017-07-17 23:13 (UTC)

Firstly thanks! Secondly, the package doesn't work against the current (4.1.60) version of the Chrome extension. It is just silently ignored. I made the following changes: pkgver=4.1.60 _chromever=${pkgver} And then ran `updpkgsums`. The package built cleanly and is now detected properly by the Chrome browser extension. (For those playing at home, this can be checked under Lastpass [icon] -> More Options -> About Lastpass.)

Det commented on 2017-06-06 14:28 (UTC)

"massive cleanup of pretty much every possible bad practice a maintainer can do. :(" Awww. :-D

toniopelo commented on 2017-05-13 09:29 (UTC)

lpchrome_linux_4.1.51 fail the md5sums check. Unable to build the package.

k2s commented on 2017-03-23 13:17 (UTC)

correct md5sum (second in PKGBUILD): 0c8ee397e4550310309bb7e8f069a892 lpchrome_linux_4.1.42-2.crx

apastuszak commented on 2017-03-23 11:37 (UTC)

==> Validating source files with md5sums... lplinux_4.1.23.tar.bz2 ... Passed lpchrome_linux_4.1.42-2.crx ... FAILED lpchrome_linux_4.1.23.crx ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp4_4.1.35a.xpi ... Passed profiles.ini ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build lastpass.

commented on 2017-03-16 17:04 (UTC)

Much appreciated. Thank you!

Det commented on 2017-03-16 16:16 (UTC)


commented on 2017-03-16 16:11 (UTC)

Oops sorry. I'm having some issues with for `lpchrome_linux_4.1.41-1.crx' (md5sum mismatch). a73aa1a26b84f7a950a21dc4204eec96 in PKGBUILD, 649f10aeb2a75506e038e3ba0794cedd from the build path.

Det commented on 2017-03-16 15:58 (UTC)

> tianyug flagged lastpass out-of-date on 2017-03-16 for the following reason: > > v4.1.42 Release note: > Tarball: > SHA-256: adb0e91f8d212d34dbb85db0b11738fe36db1a741ad5674d7070c4019a9fc75e The versions are from here:

Det commented on 2017-02-15 19:07 (UTC)

Okayh... maybe it now works.

xiong.chiamiov commented on 2017-02-15 18:38 (UTC)

Aur Targets (1): lastpass Proceed with installation? [Y/n] Edit lastpass PKGBUILD with $EDITOR? [Y/n] n Edit lastpass.install with $EDITOR? [Y/n] n ==> Making package: lastpass 4.1.23-2 (Wed Feb 15 10:37:05 PST 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found lplinux_4.1.23.tar.bz2 -> Found lpchrome_linux_4.1.40-1.crx -> Found com.lastpass.nplastpass.json -> Found lastpass_policy.json -> Found lp4_4.1.35a.xpi -> Found profiles.ini ==> Validating source files with md5sums... lplinux_4.1.23.tar.bz2 ... Passed lpchrome_linux_4.1.40-1.crx ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp4_4.1.35a.xpi ... Passed profiles.ini ... Passed ==> Extracting sources... -> Extracting lplinux_4.1.23.tar.bz2 with bsdtar -> Extracting lpchrome_linux_4.1.40-1.crx with bsdtar ==> Starting prepare()... ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package()... -> Installing for Google Chromes/Chromiums... -> Installing for Mozilla Firefoxes... install: cannot stat '': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... The build failed.

Det commented on 2017-02-15 17:35 (UTC) (edited on 2017-02-15 17:35 (UTC) by Det)

Thanks, but that downloads some super-old 3.x. Should work now.

FadeMind commented on 2017-02-15 17:30 (UTC)

1. file was not found anywhere 2. New VALID firefox XPI file URL is: 3.VALID install -Dm644 lpchrome_$_chromver.crx "$pkgdir"/usr/share/lastpass/lpchrome_$_chromver.crx NOT install -Dm644 lpchrome_linux_$_chromver.crx "$pkgdir"/usr/share/lastpass/lpchrome_linux_$_chromver.crx

Nevax commented on 2016-07-17 07:57 (UTC)

Can you add vivaldi support please ?

Det commented on 2016-06-22 13:36 (UTC)

I didn't know you were switching either after install?

Erroneous commented on 2016-06-22 11:20 (UTC)

Would it make more sense to make a command to fix LastPass after install? Maybe a lastpass-extension-fix command which could be used any time after installation instead of hard coding a user and directory into the post install script.

sebstar commented on 2016-05-04 09:10 (UTC)

Is it possible to execute (sudo -u $_user) the changes to the user plugin directories as the user themself? My $HOME is mounted on a nfsv4 network share where (thankfully) the root user doesn't have access to, so the user home directory part of the .install script fails.

Det commented on 2016-04-15 15:56 (UTC)

That's with the binary plugin. You can extract the .crx to see the one provided without it.

FadeMind commented on 2016-04-15 15:55 (UTC)

LastPass Chrome Extension version is 4.1.6, not 4.1.5.

Det commented on 2016-04-11 15:13 (UTC)

Not, if multiple?

Erroneous commented on 2016-04-11 13:49 (UTC)

I don't know if there is a standard way of doing this, but you could use the following to figure out the current user name and home directory in lastpass.install if only one user is logged in: _user=$(users | sed -e 's/ /\n/g' | grep -v root | sort | uniq) # User _home=$(eval echo ~$_user) # $HOME

Det commented on 2016-03-28 17:23 (UTC) (edited on 2016-03-28 17:24 (UTC) by Det)

"Your package lastpass [1] has been flagged out-of-date by Emmaseven [2]: md5 not correct" Which one? All pass here.

Det commented on 2016-03-26 10:22 (UTC)


FadeMind commented on 2016-03-26 07:13 (UTC)

nplastpass64 and nplastpass bin files are now in $srcdir/lplinux/ So install command should be install -Dm755 lplinux/nplastpass$_64 "$pkgdir"/etc/opt/chrome/native-messaging-hosts/nplastpass$_64

apastuszak commented on 2016-03-13 23:48 (UTC)

Since I installed the latest version, Chrome will not remember my 2 factor authentication code for 30 days. I need to re-enter it every time I re-launch Chrome.

Det commented on 2016-03-09 15:32 (UTC)

✔ NOTE: If the md5sums don't match, don't post the makepkg output. Simply flag the package.

sedwen commented on 2016-02-11 21:48 (UTC) (edited on 2016-02-11 22:15 (UTC) by sedwen)

md5sum incorrect lpchrome_linux_4.0.6-1.crx ... FAILED flagged

Det commented on 2016-02-11 20:07 (UTC)

It was a purposeful change.

FadeMind commented on 2016-02-11 19:40 (UTC)

FIXED PKGBUILD: is not available anymore for Firefox. I fixed name for CRX chrome plugin too.

spapanik21 commented on 2016-01-27 11:24 (UTC)

There are two issues with the package. First it does not install the package in opera, and second it fails to get the signing in firefox (which will be a real issue when ff46 gets released)

s83 commented on 2016-01-25 22:26 (UTC)

Can you add support for opera and opera-developer? thank you in advance

Det commented on 2016-01-18 21:37 (UTC)

Oh yeah.

radiomike commented on 2016-01-18 21:34 (UTC)

PKGBUILD and lastpass.install currently broken due to change of name for firefox plugin. Other references to lp_linux_$_ffver.xpi need updating to lp4_$_ffver.xpi? One in _firefox_package() function and at least 2 in lastpass.install

Det commented on 2016-01-18 18:06 (UTC)

@harpchad, Pastebin, please.

harpchad commented on 2016-01-18 16:10 (UTC) (edited on 2016-01-18 16:12 (UTC) by harpchad)

Here's a patch that will allow it to build with the updated chrome and firefox versions as of 1/18: --- PKGBUILD.o 2016-01-18 10:07:17.000000000 -0600 +++ PKGBUILD 2016-01-18 10:11:29.645686287 -0600 @@ -3,9 +3,9 @@ pkgname=lastpass pkgver=4.0.0 _universal=$pkgver-1 # Version of the universal installer: -_chromver=4.0.0-1 # The actual extensions' versions -_ffver=3.2.42-1 -pkgrel=1 +_chromver=4.0.3-1 # The actual extensions' versions +_ffver=4.0.1-1 +pkgrel=2 pkgdesc="The Universal LastPass installer for Firefox, Chrome, and Opera" arch=('i686' 'x86_64') url="" @@ -29,14 +29,14 @@ 'com.lastpass.nplastpass.json' 'lastpass_policy.json' # Firefox - "lp_linux_$_ffver.xpi::$url/lp_linux.xpi" + "lp_linux_$_ffver.xpi::$url/lp4.xpi" 'profiles.ini') noextract=("lp_linux_$_ffver.xpi") -md5sums=('0fab4037becea4f1482b42a15182cddd' +md5sums=('94672a14e39bd7c9022fcf23837a08a4' '009f2d1a3ac25eb7a3a18f5ad0fc4f53' '151251e415bccdffc1dc0df592d1d7e1' '9af777d2eea8e67ad332235718a7653d' - '632703e30bc26865f15f87690e516105' + 'd4a8679fe4d8cedf1369d90eb7a0b0b5' 'd0f555a644484baccf649f7969794ece') # 64-bit?

txtsd commented on 2016-01-15 09:07 (UTC)

==> Validating source files with md5sums... lpchrome_linux_4.0.0-1.crx ... FAILED

Det commented on 2016-01-13 13:51 (UTC) (edited on 2016-01-13 13:51 (UTC) by Det)

@xdevla, sadly, you are so mistaken. You can flag it, when the md5sums don't match no more.

felixsanz commented on 2016-01-04 18:32 (UTC)

broken ==> Validating source files with md5sums... lp_linux_3.2.40-1.xpi ... FAILED

widowild commented on 2015-12-26 19:31 (UTC)

003ed00c79efd54166841ac746c831f6 lp_linux_3.2.40-1.xpi

dmp1ce commented on 2015-12-17 16:09 (UTC)

I'm getting "LastPass could not be verified for use in Firefox and has been disabled." in Firefox. Does the package need to be updated?

txtsd commented on 2015-12-17 03:56 (UTC)

md5sum lplinux_3.2.16-3.tar.bz2 009f2d1a3ac25eb7a3a18f5ad0fc4f53

Pietro_Pizzi commented on 2015-10-01 20:31 (UTC)

> md5sum /tmp/yaourt-tmp-${USER}/aur-lastpass/ 352e1d7e1b5a4946da19581ab60945b3 /tmp/yaourt-tmp-[user]/aur-lastpass/lplinux_3.2.16.tar.bz2

sensorback commented on 2015-10-01 06:35 (UTC)

I guess this one just installs lastpass on all common browsers, so you don't have to install the extensions manually in each browser? Or does this package give you any additional benefits?

Det commented on 2015-09-30 21:14 (UTC)

Should provide a version that doesn't work.

andykluger commented on 2015-09-30 21:13 (UTC)

Can anyone tell me exactly what this offers over just the non-binary browser extensions (particularly the firefox one)?

Pietro_Pizzi commented on 2015-09-30 17:21 (UTC)

> md5sum /tmp/yaourt-tmp-${USER}/aur-lastpass/lp_linux_3.2.16.xpi c69d39cfde945b8b3d4072540d2abb87 /tmp/yaourt-tmp-[user]/aur-lastpass/lp_linux_3.2.16.xpi

sirrus233 commented on 2015-09-05 00:56 (UTC)

Flagged out of date, because the lpchrome_linux checksum is wrong.

Det commented on 2015-08-22 15:04 (UTC)

Whoops. But build with --skipinteg, and it doesn't matter, right?

FadeMind commented on 2015-08-22 14:45 (UTC)

bad checksums...

Det commented on 2015-08-22 14:20 (UTC)

Why didn't you flag it?

Pietro_Pizzi commented on 2015-08-21 09:30 (UTC)

> md5sum /tmp/yaourt-tmp-[user]/aur-lastpass/lpchrome_linux_3.2.21.crx 87fc7adfd303a0d6cb6faa2b790988a3 /tmp/yaourt-tmp-[user]/aur-lastpass/lpchrome_linux_3.2.21.crx

Det commented on 2015-08-17 20:57 (UTC)

It was right until they updated it.

zman0900 commented on 2015-08-17 20:47 (UTC)

The md5sum for lp_linux_3.2.16.xpi is wrong.

Det commented on 2015-07-24 16:58 (UTC)

You don't need to link new MD5SUMS, because you can just build with --skipinteg.

sabrsorensen commented on 2015-07-24 16:57 (UTC)

New md5sums as of 2015-07-24 are as follows: e6fd852af9807078895c815a8e81bfbf lpchrome_linux.crx e524a12752284b93979369b463a8f60f lp_linux.xpi Working PKGBUILD at

drewofdoom commented on 2015-06-02 18:42 (UTC)

Working PKGBUILD for the latest version (as of 2015-06-02)

i.o commented on 2015-05-11 06:56 (UTC)

lp_linux_3.1.95-1.xpi ... FAILED I'm sorry, I don't know how to find what it should be.

w1ngnutt commented on 2015-04-21 12:40 (UTC)

lpchrome_linux_3.1.97-1.crx ... FAILED Should be 9758c09c8b2198933536e2562f3b7c5c Thanks.

pancho commented on 2015-04-20 10:48 (UTC)

lplinux_3.1.92.tar.bz2 ... FAILED Should be 560746ff6a325200de014a0a599a69bb Thanks!

uscountrylinux commented on 2015-04-04 23:40 (UTC)

lpchrome_linux_3.1.95-1.crx ... FAILED Should be 4403b10effc2775f25f7ce16a87bd1de

Det commented on 2015-03-24 22:37 (UTC)

If you create new profiles, or have multiple users, then yes, but most people don't. The exception with this package is that it isn't just one add-on/extension for a single browser. It's the extension + plug-in for all applicable browsers.

eschwartz commented on 2015-03-24 22:32 (UTC)

Because I thought the idea of packaging an extension (:o) is in order to integrate it directly into Firefox, otherwise why not simply install it the usual way? Similar to why I have Adblock Plus and HTTPS Everywhere installed globally, via similar packages. A package that merely bootstraps a per-profile user-level install would have to be re-installed every time anyone created a new profile, which makes it somewhat pointless IMHO. It also needs to be installed as each user, to be useful.

Det commented on 2015-03-24 04:28 (UTC)

You mean the add-on, not the (binary) plugin? If it can be updated by a user afterwards without having to update this package, then why not. I haven't gotten around to even making the Chrome extension install properly, as I kept getting tired of the confusing inconsistent results.

eschwartz commented on 2015-03-24 04:21 (UTC)

Is there any particular reason why the Firefox plugin isn't just installed to the global extensions directory? Works fine for me. lastpass.install -- PKGBUILD ---------- (Also I fixed the Chrome version and reported it, this comment isn't about that, I promise! :D)

Det commented on 2015-03-05 10:26 (UTC)

They finally bumped the universal installer version as well. @damianj, "evolved" is maybe a bit misleading.

Pietro_Pizzi commented on 2015-03-05 01:59 (UTC)

lp_linux_3.1.92-1.xpi ... FAILED

Det commented on 2015-03-04 19:17 (UTC)

All right, already.

bgta commented on 2015-03-04 07:18 (UTC)

lp_linux_3.1.77-1.xpi FAILED New MD5: 4be910f80dea4bf61f12f8f214519500 lp_linux_3.1.77-1.xpi

Det commented on 2015-02-27 18:29 (UTC)

By the way, came across this while trying to make this work for Chrome (the "Allow access to file URLs" that I always tick):

Det commented on 2015-02-26 12:12 (UTC)

Updated, and the Firefox insanity is now fixed. The deprecated Opera extension is also removed. I'm still working on getting the Chrome extension work for both.

Det commented on 2015-02-11 23:51 (UTC)

Yeah, just the flg's fine for me. I don't require 4 comment notifications on top of it :).

thevdude commented on 2015-02-11 23:43 (UTC)

lpchrome_linux_3.1.89-1.crx ... FAILED Looks like this has been updated, there's a new hash: 4f6f3c1f67a892abc82545edd1536ad5 lastpass-3.1.89-1.oex ... FAILED Looks like this has been removed, the installer uses the chrome extension for opera now. Adding the new md5 and removing opera specific parts from the PKGBUILD and .install did not install lastpass for me on google-chrome-beta

oblique commented on 2015-01-22 08:48 (UTC)

Ok I found what I had to do in Chromium: 1) install this package 2) install Lastpass from Chrome Store 3) Login in Lastpass then click on its icon and go: Tools -> About, click "Enable Native Messaging" and then restart Chromium. I don't know if there is a more automatic way.

oblique commented on 2015-01-22 08:29 (UTC)

Also I noticed that you don't have "chrome-extension://hgnkdfamjgnljokmokheijphenjjhkjc/" in allowed_origins. They have it in their install script.

oblique commented on 2015-01-22 08:05 (UTC)

Lastpass is not shown in Chromium. Should I do anything else after I install this package? I also don't see it in chrome://extensions/

Det commented on 2015-01-18 16:10 (UTC)

There's currently no support for multiple profiles. I'll fix it soon.

andykluger commented on 2015-01-18 03:50 (UTC)

I just upgraded this package and confirmed this process kills my profiles. Here's the before and after contents of my profiles.ini: I don't remember if I created the lastpass profile or if it was generated by this package and I just held on to it.

Det commented on 2015-01-16 19:20 (UTC)

Profiles.ini is only touched when it doesn't point to a default profile, or it doesn't exist (e.g. if Firefox isn't even installed). Otherwise the extension can't be extracted anywhere reliable, because a profile name is always decided at random. Have you ever had a look at the contents of the blown out profiles.ini?

andykluger commented on 2015-01-16 17:55 (UTC)

I've found that every so often my firefox profiles.ini gets clobbered and I have to recreate it to access my profiles. I've taken to backing it up elsewhere and copying it back over whenever that happens. Is it possible this package is responsible for the clobbering? Why does it provide its own profiles.ini?

Det commented on 2014-12-31 04:24 (UTC)

Thanks, @Carceri.

Det commented on 2014-12-25 12:37 (UTC)

Again, flag it.

Pietro_Pizzi commented on 2014-12-25 12:06 (UTC)

==> Validating source files with md5sums... lpchrome_linux_3.1.77-1.crx ... Passed lplinux_3.1.50-2.tar.bz2 ... FAILED com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.75-1.xpi ... Passed profiles.ini ... Passed lastpass-3.1.77-1.oex ... Passed prefs.dat ... Passed widgets.dat ... Passed

Det commented on 2014-12-15 22:59 (UTC)

K, you can just flag it.

gverilla commented on 2014-12-15 22:58 (UTC)

The build fails on the .xpi-checksum this time. Btw, the verion should be 3.1.75, not 3.1.54 anymore... ==> Validating source files with md5sums... lpchrome_linux_3.1.65-1.crx ... Passed lplinux_3.1.50-2.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.54-1.xpi ... FAILED profiles.ini ... Passed lastpass-3.1.65-1.oex ... Passed prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check!

allen875 commented on 2014-10-30 20:34 (UTC)

Build fails the validity check. ==> Validating source files with md5sums... lpchrome_linux_3.1.63-1.crx ... FAILED lplinux_3.1.50.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.54-1.xpi ... Passed profiles.ini ... Passed lastpass-3.1.63-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check!

Det commented on 2014-10-25 08:29 (UTC)

3.1.50-9: Fix ownership of ~/.lastpass/ The second group doesn't matter, as long as the owner is the user itself.

altercation commented on 2014-10-25 01:34 (UTC)

Just installed this and confirmed that the .lastpass and .opera* directories are not showing correct ownership. .lastpass was root:root and .opera was user:root. I did a quick chown -R username:usergroupname on .lastpass (didn't bother with .opera* since I don't use it) and the trusted computer functionality works again.

Det commented on 2014-10-19 10:34 (UTC)

Hmm, my scripts are actually already supposed to do that. Which browsers' files, and specifically which files, are owned by root?

Edholm commented on 2014-10-16 16:27 (UTC)

It seems the files/dirs installed in the home directory are owned by root and therefore breaks some functionality, such as "Trusted computer". Maybe chown after moving them?

Det commented on 2014-08-21 16:55 (UTC)

Really no need to post that twice in a row..

square252 commented on 2014-08-21 06:22 (UTC)

==> Überprüfe Gültigkeit der Quell-Dateien mit md5sums... lpchrome_linux_3.1.53-1.crx ... FEHLGESCHLAGEN lplinux_3.1.50.tar.bz2 ... Durchgelaufen com.lastpass.nplastpass.json ... Durchgelaufen lastpass_policy.json ... Durchgelaufen lp_linux_3.1.50-3.xpi ... Durchgelaufen profiles.ini ... Durchgelaufen lastpass-3.1.53-1.oex ... FEHLGESCHLAGEN prefs.dat ... Durchgelaufen widgets.dat ... Durchgelaufen ==> FEHLER: Eine oder mehrere Dateien überstanden nicht die Gültigkeits-Prüfung! ==> FEHLER:Makepkg konnte lastpass nicht erstellen.

commented on 2014-08-20 23:48 (UTC)

More file validation problems: ==> Validating source files with md5sums... lpchrome_linux_3.1.53-1.crx ... FAILED lplinux_3.1.50.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.50-3.xpi ... Passed profiles.ini ... Passed lastpass-3.1.53-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check!

Det commented on 2014-08-20 14:49 (UTC)

Updated with Cygwin64.

brettski commented on 2014-08-20 14:45 (UTC)

==> Validating source files with md5sums... ... lp_linux_3.1.50-2.xpi ... FAILED ... ==> ERROR: One or more files did not pass the validity check!

Det commented on 2014-08-08 23:36 (UTC)

Recent changes to LastPass: v3.1.50/3.1.51 - August 7th 2014 -- Chrome/Firefox/IE/Safari/Yandex New: Auto-suggest folder name for newly saved popular sites. Security: Change http to https saved urls for more secure filling. Security: Tightened CSP rules. Security: Disallow automatic filling of iframes if domain of frame is different than top page's domain. Improved: Improved Create Account Wizard in Chrome/Safari. Improved: Show first time overlay. Improved: Overview pages in vault when user has not added data. Improved: UI of online security challenge. Fixed: Prevent high cpu usage when setup fingerprint authentication. -

Det commented on 2014-08-08 03:11 (UTC)

- Recent changes to LastPass: v3.1.44/3.1.45 - July 22nd 2014 -- Chrome/Safari/Yandex Improved: Further enhancements to Password Generator UI/UX. Resolved: Improved handling of filling in iframes and framesets. Resolved: Better detection of hidden fields when filling. v3.1.42/3.1.43 - July 15th 2014 -- Chrome/Safari/Yandex Improved: Password Generator UI/UX improvement. Resolved: Show warning when try to remember master password. Resolved: Better handling of filling in iframes.

Det commented on 2014-07-04 12:52 (UTC)

Another silent revision update.

neverfox commented on 2014-07-04 04:29 (UTC)

A couple of fails failed the md5sums check. ==> Validating source files with md5sums... lpchrome_linux_3.1.41-1.crx ... FAILED lplinux_3.1.40.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.40-1.xpi ... Passed profiles.ini ... Passed lastpass-3.1.41-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build lastpass.

Det commented on 2014-07-03 11:40 (UTC) v3.1.40/3.1.41 - July 2nd 2014 -- Chrome/Safari/Yandex New: SecurID support as a second factor. Resolved: Fix for favicons for Shared Folder sites in local vault. Resolved: Better handling of login forms in iframes. Resolved: Better detection of sites with login forms spread across multiple pages.

woodsb02 commented on 2014-07-03 10:21 (UTC)

==> Validating source files with md5sums... lpchrome_linux_3.1.33-1.crx ... FAILED lplinux_3.1.40.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.40-1.xpi ... Passed profiles.ini ... Passed lastpass-3.1.33-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check!

Det commented on 2014-07-01 18:48 (UTC)

I'm assuming it works now.

Det commented on 2014-07-01 15:45 (UTC)

That should never happen. I'll look into that some more.

widowild commented on 2014-06-29 20:29 (UTC)

Hello, i use yaourt and i have a problem: (1/1) mise à jour de lastpass [###########################################] 100% Installing Mozilla Firefox leftovers... install : option invalide -- '/' Saisissez « install --help » pour plus d'informations. bsdtar: could not chdir to '-/extensions/' /tmp/alpm_VgKKxg/.INSTALL: ligne 30: -/prefs.js: Aucun fichier ou dossier de ce type chown : option invalide -- '/' Saisissez « chown --help » pour plus d'informations. chown : option invalide -- '/' Saisissez « chown --help » pour plus d'informations. Installing Opera leftovers...

Det commented on 2014-06-28 13:59 (UTC)

v3.1.40 - June 26th 2014 -- Firefox/IE New: Convert Folder in Vault to Shared Folder. New: Enterprise - policy to force user to setup linked account. New: Enterprise - check for master password reuse. New: Adjust Security Challenge results for sites with recent vulnerabilities. New: LastPass OpenSSL CCS checker tool available. Resolved: Fix for Google login page. Resolved: IE instant sync now works. Resolved: Improved firefox addon performance. Resolved: Prevent offer to add new sites if already present in vault. Resolved: Better handling of change password forms.

Det commented on 2014-06-16 00:09 (UTC)

No changelog for 3.1.33 yet: v3.1.30/31 - June 12th 2014 -- Chrome/Safari/Yandex New: Convert Folder in Vault to a Shared Folder. New: Annotate shared items in the vault. Improved: Better filling for sites with random field names. Resolved: Fix for accessing applications in toolbar menu. Resolved: Fix for password generator button in safari. Resolved: Prevent error in console. Resolved: Fix for disable offline access and yubikey. v3.1.20/21 - May 5th 2014 -- Chrome/Safari Improved: Action icon for folders in vault. Improved: Faster favicon retrieval when add new sites. Improved: Better memory usage and overall performance for pages with a large number of frames (including Resolved: Fixed local updates to safari when editing shared folders.

Det commented on 2014-06-04 22:42 (UTC)

We just hit Summer here in Finland? Also, I have quite a lot of other packages and places I visit, so for me to look into a feature I've never ever even heard of that isn't working too good might take me some time - especially if the 'looking in' thing takes some time even in and of itself. I'll try to remember the important cultural differences for the next time I meet an Aussie, though.

Xavion commented on 2014-06-04 22:21 (UTC)

Thanks for not taking 11 days to reply to my comment this time! I agree that your English, in your second reply, was pretty bloody good. Also, whatever you've done to the PKGBUILD, the problem is now fixed at my end. The initial confusion was due to your use of "I don't get that". Native English speakers often intend "get" to mean "understand" in that case. If you had've said "that doesn't happen here", all ambiguity would have been removed. By the way, I imagine it'd be pretty easy for those living in Finland to "chill out". However, the situation is very different here in Australia. I encourage you to try it some time and see how cool you are down under :-).

Det commented on 2014-06-04 13:33 (UTC)

Excuse me? What I'm saying to you is that after _just_ trying it out myself, I didn't have such a problem. If you do, then all I can suggest is a rebuild. As for English, while we don't have that as a native language here in Finland, I can promise you that even for a Finn I actually speak it pretty damn well. So, chill out, try a rebuild, and then you can come back to report me the results. We can go from there. But I'm telling you right now that if you come back with that same attitude, you're on your own.

Xavion commented on 2014-06-04 05:58 (UTC)

No, I wouldn't have notified you of the problem if your package had worked correctly. Is English your second language or something? I'm saying that the problem doesn't occur when I install LastPass via its own "" script (i.e. by downloading the tarball manually). This means your PKGBUILD is doing something differently that's preventing LastPass from remembering (Google Authenticator) trusted computers.

Det commented on 2014-06-04 00:56 (UTC)

I don't get that, so I guess I accidentally fixed it?

Xavion commented on 2014-05-25 00:45 (UTC)

This package doesn't remember trusted computers when using the Google Authenticator multifactor option in Chrome. Whenever I log-in to LastPass, I'm prompted to enter a Google Authenticator code even though my computer is trusted. This wasn't happening before I installed your package, and it doesn't occur after I use the standard "" script.

Det commented on 2014-04-22 19:47 (UTC)

You'd also wanna bump the pkgrel.

amkan13 commented on 2014-04-22 19:39 (UTC)

instead of the md5sum for the failed file just enter 'SKIP' for the time being until package is fixed when editing the PKGBUILD

dabai commented on 2014-04-22 15:48 (UTC)

lpchrome_linux_3.1.13-1.crx ... Passed lplinux_3.1.2.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.1-2.xpi ... FAILED profiles.ini ... Passed lastpass-3.1.13-1.oex ... Passed prefs.dat ... Passed widgets.dat ... Passed

Det commented on 2014-04-13 06:54 (UTC)

Just the fact that they don't match means it's out of date. E: The 3.1.8 is the 'actual' version. 3.1.9 means you also got the binary component (we get that from the universal installer: (chrome:plugins -> Lastpass Plugin - /usr/lib/mozilla/plugins/libnplastpass(64).so). For reference: "Do I have the binary plugin installed?": "What does binary support for extensions mean?":

PonsAsinorem commented on 2014-04-13 03:24 (UTC)

LastPass + binary is 3.1.9 for Chrome. And this confirms out of date (but says 3.1.8)

sebstar commented on 2014-04-11 20:49 (UTC)

Updated to 3.1.1? ==> Validating source files with md5sums... lpchrome_linux_3.1.1-2.crx ... FAILED lplinux_3.1.0.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lp_linux_3.1.1-2.xpi ... Passed profiles.ini ... Passed lastpass-3.1.1-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build lastpass.

Det commented on 2014-04-10 20:42 (UTC)

Well, don't run it as root?

workdowg commented on 2014-04-10 20:33 (UTC)

BTW, answering yes gets the same build failure.

workdowg commented on 2014-04-10 20:32 (UTC)

==> NOTE: Makepkg is running as root. The extensions will not be available to a regular user. -> Continue? (Y/n)n ==> ERROR: Aborted by user! Exiting... The build failed. Any ideas?

Det commented on 2014-04-10 09:35 (UTC)

lol 3.1.0-4 - Changed the permissions of the following to 755: - /etc/opt/chrome/native-messaging-hosts/nplastpass(64) - /usr/lib/mozilla/plugins/libnplastpass(64).so

teekay commented on 2014-04-10 08:45 (UTC)

Could you please set the binary component for chrome to 755? Currently from chrome stdout: --- LaunchProcess: failed to execvp: /etc/opt/chrome/native-messaging-hosts/nplastpass64 --- Caused by: install -Dm644 nplastpass${_64} ...

Det commented on 2014-04-09 10:08 (UTC)


joren commented on 2014-04-08 16:13 (UTC)

New version of lp_linux, hash: 2f52b11cadf94eb1f70e5b2a184d0d00

Det commented on 2014-03-15 18:00 (UTC)

You could try reinstalling with: # pacman -U /var/cache/pacman/pkg/lastpass-3.1.0-2-* If it's chromium-browser-bin, then they probably broke it in trunk.

daglamier22 commented on 2014-03-15 14:28 (UTC)

Stopped working in Chromium after updating last night, doesn't show up in extensions list. Does work in Firefox however. Any ideas?

Det commented on 2014-03-04 18:01 (UTC)


harpchad commented on 2014-03-04 17:41 (UTC)

Looks like lp_linux.xpi has been updated to 3.1.1: ==> Validating source files with md5sums... lplinux_3.1.0.tar.bz2 ... Passed com.lastpass.nplastpass.json ... Passed lastpass_policy.json ... Passed lpchrome_linux_3.1.1-1.crx ... Passed lp_linux_3.1.0-1.xpi ... FAILED profiles.ini ... Passed lastpass-3.1.1-1.oex ... Passed prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check! <RDF:Description RDF:about="urn:mozilla:install-manifest"> <em:id></em:id> <em:version>3.1.1</em:version> <em:type>2</em:type> <em:unpack>true</em:unpack> . . .

Det commented on 2014-02-20 11:13 (UTC)

Yeah, I've been getting that too. Happens once a while. The profile fix was just to get the installation to complete. I've had doubts from time to time as well, as to whether my complicated install is actually doing what it's supposed to, but a quick verification of removing and installing the extension from inside the browser always proved me wrong. It doesn't interfere with the package, either, so feel free to do it, if you have problems. You only need to put in your login details anyway.

jpaechnatz commented on 2014-02-20 08:22 (UTC)

now building and updating without errors. thanks. the last two days I'm getting...could not connect to server/offline mode...messages from the firefox extension, but I guess it's not related to this...

Det commented on 2014-02-20 08:08 (UTC)

I fixed the Firefox profile check, if ~/.mozilla/firefox/profiles.ini doesn't state the 'default' in the name. Is it still working?

jpaechnatz commented on 2014-02-20 07:10 (UTC)

Prepare() is failing, even makepkg -L does not provide more information.

Det commented on 2014-02-20 03:40 (UTC)

Updated to 3.1.0: - The libnplastpass(64).so libraries are no longer included in the .crx - Packaged & uploaded the v3.1.1 .crx to Dev-Host, since hasn't been updated (v3.0.19). Just tell me, if it isn't working - Added the '/etc/opt/chrome/native-messaging-hosts/nplastpass(64)' binary (I don't know, if they've moved to that from the .so's) → Added 'com.lastpass.nplastpass.json' so that Chrome/Chromium can use it - Removed 'hdokiejnpimakedhajhdlcegeplioahd.json' (unnecessary)

Det commented on 2013-12-24 22:39 (UTC)

Yeah, can't reproduce that here. All I can suggest is to reinstall (or just update) the package. If for some reason even that doesn't work, you can try reinstalling the extension from the browser itself.

Det commented on 2013-12-24 13:20 (UTC)

It shouldn't be. I'll try to find out what's wrong when I have time.

chetwisniewski commented on 2013-12-23 01:40 (UTC)

It is now broken in Firefox. When you attempt to login to a site you get an invalid password regardless of input. I can log in to Lastpass itself, but it will not fill in passwords.

Det commented on 2013-12-21 20:07 (UTC)

A couple of fixes: * fix the sed command for Firefox → change the default profile from 'lastpass' to 'lastpass.default' as well * use 'bsdtar' instead of 'unzip'

MikeDacre commented on 2013-12-20 00:52 (UTC)

I think the issue with the "sed: -e expression #5, char 71: unterminated `s' command" error is multiple google chrome profiles. I recommend changing the line: -e "s,_mozilla= *[^ ]*,_mozilla=/home/$USER/.mozilla/firefox/$(sed -n 's/^Path=//p' /home/$USER/.mozilla/firefox/profiles.ini)/," \ to: -e "s,_mozilla= *[^ ]*,_mozilla=/home/$USER/.mozilla/firefox/$(sed -n 's/^Path=//p' /home/$USER/.mozilla/firefox/profiles.ini | grep default)/," \ That change will only include the default profile. Alternatively, some users may wish to use a shell script to create an array of all profiles and install lastpass into every single profile.

jevonearth commented on 2013-12-18 20:23 (UTC)

Build fails. ==> Extracting sources... -> Extracting lpchrome_linux_3.0.19-1.crx with bsdtar ==> Starting prepare()... sed: -e expression #5, char 71: unterminated `s' command ==> ERROR: A failure occurred in prepare(). Aborting...

jpaechnatz commented on 2013-12-18 13:20 (UTC)

Beginne prepare()... sed: -e Ausdruck #5, Zeichen 76: Nicht beendeter `s'-Befehl

MishY commented on 2013-11-22 19:39 (UTC)

Thank you Det for updating the package.

harpchad commented on 2013-11-21 15:24 (UTC)

Looks like lp_linux has been bumped to 3.0.12: ==> Validating source files with md5sums... lpchrome_linux_3.0.13-1.crx ... Passed lp_linux_3.0.10-1.xpi ... FAILED profiles.ini ... Passed lastpass-3.0.13-1.oex ... Passed prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check! grep "var version" install.js var version = "3.0.12";

wtribe commented on 2013-11-20 03:20 (UTC)

Oh oh... ==> Validating source files with md5sums... lpchrome_linux_3.0.11-1.crx ... FAILED lp_linux_3.0.10-1.xpi ... Passed profiles.ini ... Passed lastpass-3.0.11-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build lastpass. ==> Restart building lastpass ? [y/N] ==> --------------------------------- ==> ==> ERROR: unable to update

Det commented on 2013-11-17 09:54 (UTC)

Fixed both.

adrianx commented on 2013-11-14 07:59 (UTC)

I think I figured out my "sed: can't read ../lastpass.install: No such file or directory" problem. My BUILDDIR was in a non-standard place. I've changed it back to the default "/tmp/makepkg" and it now works.

zbyshek commented on 2013-11-11 16:05 (UTC)

Please fix the .install file Removing from Google Chromes/Chromiums... Removing from Mozilla Firefoxes... /tmp/alpm_eCzWSp/.INSTALL: command substitution: line 120: syntax error near unexpected token `(' /tmp/alpm_eCzWSp/.INSTALL: command substitution: line 120: `ls -d ~/.mozilla/firefox/lastpass*/!(extensions|prefs.js) 2>&- | wc -l)' error: command failed to execute correctly

Det commented on 2013-11-09 07:32 (UTC)

No problem, but it means we have newer versions so we gotta use them: The checksums are also automatically handled by 'updpkgsums' in my script.

siliconmeadow commented on 2013-11-09 07:20 (UTC)

All three of the downloads from lastpass failed the checksums. Here's a patch to PKGBUILD.txt with md5sums that worked for me. Thanks for your efforts in maintaining this, btw! :-)

Det commented on 2013-11-08 20:47 (UTC)

Because, as already stated in the comment history you didn't see fit to Ctrl+F at, that's the version of the "LastPass Universal Linux Installer":

commented on 2013-11-08 20:45 (UTC)

If you have 3.0.5, 3.0.5 and 3.0.1 as versions why not match the minor version (actually 3.0.1) instead of using 3.0.0?

barryfm commented on 2013-11-07 12:53 (UTC)

3.0.0-2 Still fails validation tests. ==> Validating source files with md5sums... lpchrome_linux_3.0.3-1.crx ... Passed lp_linux_3.0.1-1.xpi ... FAILED profiles.ini ... Passed lastpass-3.0.3-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check!

jevonearth commented on 2013-11-06 15:32 (UTC)

Checksums are not matching; ==> Validating source files with md5sums... lpchrome_linux_3.0.1-1.crx ... Passed lp_linux_3.0.0-1.xpi ... FAILED profiles.ini ... Passed lastpass-3.0.1-1.oex ... FAILED prefs.dat ... Passed

Det commented on 2013-11-05 18:38 (UTC)

Stop w***ing and just f*cking flag it. Thank-you.

jaudet commented on 2013-08-25 13:28 (UTC)

Works. Thanks you.

Det commented on 2013-08-24 22:37 (UTC)


jaudet commented on 2013-08-22 14:58 (UTC)

Experiencing checksum issues.

Det commented on 2013-08-09 16:25 (UTC)

Then you're doing something terribly wrong. You don't have lastpass.install in your $srcdir (same location as the PKGUBILD).

adrianx commented on 2013-08-06 10:38 (UTC)

Hi For some reason I can't install this package at all: ==> Starting prepare()... sed: can't read ../lastpass.install: No such file or directory ==> ERROR: A failure occurred in prepare(). Aborting... The build failed.

bwrsandman commented on 2013-07-19 21:18 (UTC)

Good points. It's funny about the pkgver. I was suggesting that we use sha256 instead of md5 since this is a sensitive application. I am by no means criticizing you. You're doing a top job! :D

Det commented on 2013-07-19 15:38 (UTC)

The split package()s is sort of nice but the pkgver and the sha256sums aren't :D. There's no reason _at all_, ever, to just add some new checksums to a PKGBUILD and then leave the previous ones. SHA256 is far superior to MD5 and will probably not fail in the next 10 years so why would we need both? And the reason for not switching to them is that although MD5 is clearly collision vulnerable and breaking it is easy, the LastPass servers aren't. Doing that and uploading fake extensions to them isn't really realistic. Also with the pkgver I follow the one they provide in: (titled "LastPass Universal Linux Installer").

bwrsandman commented on 2013-07-11 20:25 (UTC)

The sed command is broken in your PKGBUILD. Here's an updated and simplified one. Fixed sed, upped pkgver to 2.0.25, sha256sums added split parts of package() to smaller functions: prepare() _chrome_package() _firefox_package() and _opera_package() so it's easier to read and maintain

commented on 2013-06-10 15:02 (UTC)

md5sums=('132ed9bd99ed5720f17720bec8282368' # lpchrome_linux_$_chromver.crx '9145a1e1bfb7fef6fae16d46f57a29dd' # lp_linux_$_ffver.xpi '08f0ef46608ca1811029e43ef0650790' # profiles.ini 'e7c7f3f54ecfc96ca874e78f33fb62b3' # lastpass-$_opver.oex '45733a855b9d2f0b507d6ed67b79d395' # prefs.dat '92a87534f8c36a3e21ed128163b98945') # widgets.dat ______________________________________________________________ modify: md5sums=('132ed9bd99ed5720f17720bec8282368' # lpchrome_linux_$_chromver.crx '00c0554e3852062d4bb03a4b6868c7ee' # lp_linux_$_ffver.xpi #edit this line '08f0ef46608ca1811029e43ef0650790' # profiles.ini 'e7c7f3f54ecfc96ca874e78f33fb62b3' # lastpass-$_opver.oex '45733a855b9d2f0b507d6ed67b79d395' # prefs.dat '92a87534f8c36a3e21ed128163b98945') # widgets.dat

Det commented on 2013-06-10 08:13 (UTC)

Same thing but simplified the URLs as well.

Det commented on 2013-06-03 14:12 (UTC)

Bumped the Opera extension.

ironborn commented on 2013-06-03 14:08 (UTC)

==> Building and installing package ==> Making package: lastpass 2.0.20-4 (Пн июн 3 18:05:34 MSK 2013) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... ----------------------- skipped-------------------------------------------------------------------- -> Found profiles.ini -> Downloading lastpass-2.0.21-1.oex... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2515k 100 2515k 0 0 351k 0 0:00:07 0:00:07 --:--:-- 379k -> Found prefs.dat -> Found widgets.dat ==> Validating source files with md5sums... lpchrome_linux_2.0.25-1.crx ... Passed lp_linux_2.0.20-2.xpi ... Passed profiles.ini ... Passed lastpass-2.0.21-1.oex ... FAILED prefs.dat ... Passed widgets.dat ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build lastpass. ==> Restart building lastpass ? [y/N]

Det commented on 2013-04-23 00:38 (UTC)

Updated the Firefox addon's md5sum.

vendion commented on 2013-04-22 18:39 (UTC)

Looks like one of the one of the MD5 are out of date ==> Validating source files with md5sums... lpchrome_linux_2.0.25-1.crx ... Passed lp_linux_2.0.25-1.xpi ... FAILED profiles.ini ... Passed lastpass-2.0.25-1.oex ... Passed prefs.dat ... Passed widgets.dat ... Passed

Det commented on 2013-03-27 01:03 (UTC)

2.0.20-3: Update Chrome to 2.0.25.

Det commented on 2013-03-19 16:10 (UTC)

2.0.20-2: Fix Opera removal, if widgets.dat not empty.

Det commented on 2013-02-27 15:52 (UTC)

Woops. Sorry.

commented on 2013-02-27 15:44 (UTC)

Does not install. ==> Validating source files with md5sums... profiles.ini ... FAILED==> ERROR: One or more files did not pass the validity check!

Det commented on 2013-02-20 06:23 (UTC)

The hackiest package there is. Think that's an achievement of some kind?