Package Details: enpass-bin 6.10.1.1661-1

Git Clone URL: https://aur.archlinux.org/enpass-bin.git (read-only, click to copy)
Package Base: enpass-bin
Description: A multiplatform password manager
Upstream URL: http://enpass.io/
Keywords: enpass manager password
Licenses: custom
Provides: enpass
Submitter: tadly
Maintainer: tadly
Last Packager: tadly
Votes: 82
Popularity: 0.50
First Submitted: 2015-07-16 12:04 (UTC)
Last Updated: 2024-04-17 15:21 (UTC)

Dependencies (11)

Required by (0)

Sources (1)

Pinned Comments

tadly commented on 2017-03-14 13:17 (UTC) (edited on 2020-02-25 12:19 (UTC) by tadly)

To check if there's a new version available:

curl -so- https://apt.enpass.io/dists/stable/main/binary-amd64/Packages.gz | zcat | egrep "Package|Version|SHA256" | head -n 3

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Kisuke-CZE commented on 2016-05-04 09:48 (UTC)

There is wrong pkgver in PKGBUILD. It should be pkgver=5.2.1

tadly commented on 2016-05-03 13:24 (UTC)

New version 5.2.1 is up Most important change: QT HDPI scaling is disabled by default meaning QT_AUTO_SCREEN_SCALE_FACTOR=0 is NOT necessary anymore. So if you run into scaling issues, try QT_AUTO_SCREEN_SCALE_FACTOR=1 cheers

tadly commented on 2016-05-03 07:52 (UTC)

FOUND IT! One can simply disable "strip" for packages (which I've now done) and now everything is nice and dandy :) Enjoy your working enpass everyone ;)

tadly commented on 2016-05-03 07:25 (UTC)

Very odd. It looks like that while packaging Enpass, some debug symbols get removed from /opt/Enpass/bin/EnpassHelper/EnpassHelper If you download the .deb yourself, extract it and only replace previously mentioned file (close enpass first, than start it again) the extension works just fine. As I said, I have no idea how those debug symbols get removed. If someone got an idea, don't hesitate and let me know :)

tadly commented on 2016-04-29 09:50 (UTC) (edited on 2016-04-29 09:56 (UTC) by tadly)

Kinda strange as as soon as you disable the browser extension within enpass->settings, the background.html of the extensions screams it can not connect to the socket meaning it CAN connect while the setting is enabled (At least I'd assume so). On windows it works just fine :/ I opened a thread on the Enpass forum: https://discussion.enpass.io/index.php?/topic/104-enpass-52-browser-extension-doesnt-work/

kagir commented on 2016-04-29 09:18 (UTC)

@Tadly I confirm the problem with browser extension.

tadly commented on 2016-04-29 08:17 (UTC) (edited on 2016-04-29 08:26 (UTC) by tadly)

So, update is go and scaling is still an issue, sort of.. I added a few instructions on how to fix scaling issues which will be printed once you installed the update. Basically, export QT_AUTO_SCREEN_SCALE_FACTOR=0 is our friend. How you apply the env variable is up to you. The instructions contain 3 options to pick from. Good luck everyone :) Edit: Just realized that the browser extension doesn't work anymore with the new version. Same for you guys?

tadly commented on 2016-04-28 13:31 (UTC) (edited on 2016-04-28 13:40 (UTC) by tadly)

Alright, did some more testing and symlinking Enpass/lib/libssl.so.1.0.0 to Enpass/lib/libssl.so did indeed fix the startup problems. After symlinking Enpass/lib/libcrypto.so.1.0.0 to Enpass/lib/libcrypto.so sync for https works too. Sadly scaling is still a problem and setting QT_DEVICE_PIXEL_RATIO doesn't fix that (it does affect enpass if I set it to 3 so enpass gets even bigger but setting it to 0, 1 or 2 doesn't change anything). I'll be contacting enpass myself now and see if we can get that fixed as well as I'm unable to use enpass that way Edit: Mail has been sent, let's see what happens :)

tadly commented on 2016-04-27 21:02 (UTC)

@craigacgomez Awesome, thanks for that. I'll do some testing tomorrow and than update to the new version if it works out (even though I'll be suffering from heavy scaling issues)

craigacgomez commented on 2016-04-27 18:01 (UTC)

With the help of the Enpass team, I've managed to get Enpass 5.2.0 working. I'm still having issues with the browser extensions, but the app itself works fine including sync. I used @Tadly's comments to communicate with the Enpass team and they suggested creating a symlink /opt/Enpass/lib/libssl.so which points to /opt/Enpass/lib/libssl.so.1.0.0. Here's an updated PKGBUILD based on the PKGBUILD created by @Tadly. http://pastebin.com/eR8pdZQ0