Package Details: pwsafe r5.3e23fa2-1

Git Clone URL: https://aur.archlinux.org/pwsafe.git (read-only, click to copy)
Package Base: pwsafe
Description: A commandline program for managing encrypted password databases
Upstream URL: https://github.com/nsd20463/pwsafe
Licenses: GPL
Submitter: Barthalion
Maintainer: graysky
Last Packager: graysky
Votes: 4
Popularity: 0.000000
First Submitted: 2018-01-07 16:39 (UTC)
Last Updated: 2022-03-19 12:02 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2

rwd2 commented on 2020-09-05 17:10 (UTC)

The bug has been fixed upstream, but the underlying problem is that pwsafe can't access ~/.rnd. And according to this thread it is because the pwsafe binary in your package in installed with setuid permissions (https://bbs.archlinux.org/viewtopic.php?pid=1924549#p1924549). Apparently setuid prevents the secure_getenv function in pwsafe from accessing the $HOME and $RANDFILE environment variables.

rwd2 commented on 2020-09-04 16:07 (UTC)

Reported it upstream: https://github.com/nsd20463/pwsafe/issues/19

graysky commented on 2020-09-04 14:33 (UTC)

@rwd2 - You probably want to post that as an issue upstream. I am just packaging this.

rwd2 commented on 2020-09-04 11:51 (UTC) (edited on 2020-09-04 11:56 (UTC) by rwd2)

pwsafe creates random files in home folder

Steps to reproduce:

1) run pwsafe with any valid (or no ) arguments, for example 'pwsafe -ulpE test'

Expected result:

pwsafe runs and does not create any random files in the home folder

Actual esult:

pwsafe runs as it should, but eacht time it exits it creates a single file with a random name with question marks, containing binary data, in my home folder. These files seem like they don't serve any purpose and are the result of some bug.

I have been using pwsafe for years this problem started somewhere in 2020. Tested it with current version ( 20181220-1)

output of ls -al ~/

(...)
-rw-------  1 user1 user1   1024 Sep  4 13:21 ?W????
-rw-------  1 user1 user1   1024 Sep  4 13:20 ??c

output of stat ~/*

(...)
  File: �W���
  Size: 1024        Blocks: 8          IO Block: 4096   regular file
Device: fe00h/65024d    Inode: 6292008     Links: 1
Access: (0600/-rw-------)  Uid: ( 1000/   user1)   Gid: ( 1000/   user1)
Access: 2020-09-04 13:21:17.047276447 +0200
Modify: 2020-09-04 13:21:17.047276447 +0200
Change: 2020-09-04 13:21:17.047276447 +0200
 Birth: 2020-09-04 13:21:17.047276447 +0200
  File: ��c
  Size: 1024        Blocks: 8          IO Block: 4096   regular file
Device: fe00h/65024d    Inode: 6291997     Links: 1
Access: (0600/-rw-------)  Uid: ( 1000/   user1)   Gid: ( 1000/   user1)
Access: 2020-09-04 13:20:17.720395830 +0200
Modify: 2020-09-04 13:20:17.720395830 +0200
Change: 2020-09-04 13:20:17.720395830 +0200
 Birth: 2020-09-04 13:20:17.720395830 +0200

output of

strace -o strace.log -f -tt -s 512 pwsafe -ulpE test

https://pastebin.com/G49NCdaY

microe commented on 2020-06-03 03:28 (UTC) (edited on 2020-06-05 21:54 (UTC) by microe)

I recently got a pinebook pro and wanted to use pwsafe as I have been a long time user of pwsafe on my other Linux hosts. I wasn't able to get makepkg to build pwsafe for aarch64 without updating the config.guess script. I put together a branch that shows what I had to do in two commits: https://github.com/microe/aur-pwsafe/tree/update-config.guess

« First ‹ Previous 1 2