Package Details: passwordsafe 1.04BETA-1

Git Clone URL: (read-only)
Package Base: passwordsafe
Description: Simple & Secure Password Management
Upstream URL:
Keywords: password pwsafe security yubikey
Licenses: Artistic2.0
Conflicts: passwordsafe-debian, passwordsafe-git, pwsafe, pwsafe-gui
Submitter: Namarrgon
Maintainer: Namarrgon
Last Packager: Namarrgon
Votes: 18
Popularity: 0.526040
First Submitted: 2014-05-07 13:02
Last Updated: 2018-01-29 13:28

Latest Comments

grantdb commented on 2018-02-02 04:36

thanks @intartso the gpg key was what I needed!

Jost commented on 2017-12-17 12:34

[solved] libxerces-c was recently updated to version 3.2. passwordsafe no longer builds since then. (complains about undefined symbols)

Is there a way to get it to build against the newer lib? Thanks!

Edit: never mind, was missing a symlink from to After rebuilding everything works now.

dixi_minga commented on 2017-10-28 11:49

I wrote: "I get a weird "warning" Window after Login w/o content, only an exclamation mark"

Forget it, there was an issue with my dataabase, it only opened read/only - close inside passwordsafe and reopen solved it

dixi_minga commented on 2017-10-28 11:37

xerces-x was updated 20171026, so I had to rebuild passwordsafe.

I get a weird "warning" Window after Login w/o content, only an exclamation mark

diraimondo commented on 2017-10-11 13:03

It looks that version 1.03BETA now depends on qrencode library to build.

intartso commented on 2017-09-10 13:24

webkitgtk2 took forever to compile for me. So I used downgrade:
yaourt -S downgrade
/usr/bin/downgrade webkitgtk2
# Select 1)
# Add to IgnrList

Then after trying to install passwordsafe again it said that the public key is unknown. So I added it via:
gpg --recv-keys B131423D7F2F1BB9

After that installing passwordsafe worked.

Namarrgon commented on 2017-06-16 14:23

What error do you get from makepkg? The last release was signed with a new key so you might have to import it into the keyring first.

It's one of the official mirrors and the download is signed so I see no problem here. The farther I can stay away from the mess that is the better.
Sorry for the late reply but I didn't get an email notification for your comment.

cx65783 commented on 2017-06-16 14:12

PGP-Signature cannot be validated for some reason.

mangust commented on 2017-05-28 17:58

Could someone please tell my why the source is pulled from github and not from sourceforge. The latter is the official source [1].


georgnix commented on 2017-05-15 08:29

Sigs for the new source tarballs should be available:

All comments