Package Details: pwsafe 20200906-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.000024
First Submitted: 2018-01-07 16:39
Last Updated: 2020-09-06 10:24

Latest Comments

1 2 Next › Last »

rwd2 commented on 2020-09-07 10:39

yes.

graysky commented on 2020-09-07 10:33

So the package as-is works as expected?

rwd2 commented on 2020-09-07 06:00

The developer clarified it: "There is no rand file, and there won't be one. The difference is that with the patch, you no longer get randomly names files in the current directory after running pwsafe. And since you know why, you can safely ignore the warning."

So commit 7cf95579fd0c0849749b1f1dcbd67ca143f76b61 can apparently be safely run in setuid, it will still give the 'WARNING: pwsafe unable to seed rng. Check $RANDFILE' warning, but in this case it can be ignored.

rwd2 commented on 2020-09-06 16:12

Sorry I thought it worked, but it didn't. So I commented that in the bug report.

graysky commented on 2020-09-06 15:06

20200906-1 still gives the same warning about .rnd. you need the version with the bugfix I mentioned below, so commit 7cf95579fd0c0849749b1f1dcbd67ca143f76b61

Is this true? I see you deleted the comment here so I assume 20200906-1 works?

graysky commented on 2020-09-06 10:24

@rwd2 - Thanks, try 20200906-1

rwd2 commented on 2020-09-06 06:35

The developer responded in https://github.com/nsd20463/pwsafe/issues/19 . He recommends to keep using setuid and added a patch to make it work.

rwd2 commented on 2020-09-05 17:35

Hi Graysky,

All I am saying is that if I remove setuid it works without the $RANDFILE error. I don't know if it was your choice to package it that way. Maybe check with the developer what the best solution is. I noted in the upstream bug that setuid combined with the secure_getenv function was the underlying problem.

graysky commented on 2020-09-05 17:25

@rwd2 - To be clear, you're asserting that I need to modify the PKGBUILD NOT to include the setuid flag?

rwd2 commented on 2020-09-05 17:10

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.