Package Details: passy 1.9.4+pre-1

Git Clone URL: https://aur.archlinux.org/passy.git (read-only, click to copy)
Package Base: passy
Description: Offline password manager with cross-platform synchronization
Upstream URL: https://glitterware.github.io/Passy
Licenses: GPL-3.0-or-later
Submitter: GlitterWare
Maintainer: GlitterWare
Last Packager: GlitterWare
Votes: 0
Popularity: 0.000000
First Submitted: 2022-11-04 16:26 (UTC)
Last Updated: 2025-02-24 17:53 (UTC)

Latest Comments

1 2 Next › Last »

GlitterWare commented on 2025-02-24 17:38 (UTC)

Just published v1.9.4-pre, should resolve the firefox connector problem as well.

GlitterWare commented on 2025-02-24 15:43 (UTC)

@alexmerry @yochananmarqos new builds will now include a functional instance of Passy CLI (and a native messaging json).

I had to disable binary stripping, as apparently it removes the entirety of Passy CLI's dart code contents, but I checked the result /opt directory size, and it turns out that binary stripping offers no benefits for Passy so far anyway.

Unfortunately, I forgot to test the browser extension, but I did make sure that the files are included and that Passy CLI works. If you wish, you may invoke Passy CLI via a standard passy cli call, as well as via passy_cli, which is a direct link to the CLI binary. Cheers!

alexmerry commented on 2025-01-17 20:52 (UTC)

oh, yeah, i hadn't considered that!

yochananmarqos commented on 2025-01-17 20:45 (UTC)

@alexmerry: Normally, that should be the case and should be packaged that way--like I do with my arrowdl AUR package.

However, it appears the application will install the JSON file via the included script in user space.

alexmerry commented on 2025-01-17 20:37 (UTC) (edited on 2025-01-17 20:38 (UTC) by alexmerry)

Something to note is that the JSON file should be installed to /etc/chromium/native-messaging-hosts/ (Chromium), /etc/opt/chrome/native-messaging-hosts/ (Chrome) and /usr/lib/mozilla/native-messaging-hosts/ (Firefox, but note the stock JSON file doesn't work with Firefox).

The path in the JSON file also needs updating to point to the actual installed location of pass_cli.

yochananmarqos commented on 2025-01-17 20:27 (UTC)

@alexmerry: Good catch. I didn't notice as I still haven't gotten around to creating an account yet. I've updated my PKGBUILD accordingly.

alexmerry commented on 2025-01-17 18:52 (UTC)

This package doesn't install passy_cli (or the native messaging script and json file). Could this be why the browser extension says the connector can't be found?

GlitterWare commented on 2024-03-24 15:43 (UTC)

Apologies, the groups() array has now been removed.

Regarding ARM64 support, I am almost certain that it won't run on ARM64 in its current state as the package Passy uses to access the Argon2 library only provides x86_64 binaries and Argon2 needs to be built from source on ARM machines (which is what's done to compile Passy CLI for ARMv7).

yochananmarqos commented on 2024-03-23 23:35 (UTC) (edited on 2024-03-23 23:35 (UTC) by yochananmarqos)

@GlitterWare: I have not yet tested it on ARM64 either, however you already had variables regarding it.

Please remove the groups() array, that is only for my own personal use in my GitHub repo.

GlitterWare commented on 2024-03-23 23:18 (UTC)

Hello yochananmarqos! Thank you kindly for the quality improvements you have provided. They have been reviewed and committed to Passy AUR packages. While you have addressed the lack of aarch64 builds, Passy won't fully support aarch64 this way yet due to lack of Argon2 aarch64 binaries (user account creation / login will not work correctly). I may address this in a future commit soon, although I do not have an aarch64 system set up to test this myself as of today.

1 2 Next › Last »