nsd20463 / pwsafe Goto Github PK

$ make check
g++ -Wall -o pwsafe pwsafe.o -lX11 -lcrypto
pwsafe.o: In function emit(secstring const&, char const*, secstring const&)': pwsafe.cpp:(.text+0x2d2f): undefined reference to _XA_CLIPBOARD'
pwsafe.cpp:(.text+0x2d41): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x3565): undefined reference to _XA_TARGETS'
pwsafe.cpp:(.text+0x3577): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x35c3): undefined reference to _XA_TARGETS'
pwsafe.cpp:(.text+0x35d5): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x35e3): undefined reference to _XA_TIMESTAMP'
pwsafe.cpp:(.text+0x35f5): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x3603): undefined reference to _XA_TEXT'
pwsafe.cpp:(.text+0x3615): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x362a): undefined reference to _XA_TARGETS'
pwsafe.cpp:(.text+0x363c): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x368b): undefined reference to _XA_TIMESTAMP'
pwsafe.cpp:(.text+0x369d): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x36ae): undefined reference to _XA_TIMESTAMP'
pwsafe.cpp:(.text+0x36c0): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x3710): undefined reference to _XA_TEXT'
pwsafe.cpp:(.text+0x3722): undefined reference to XmuInternAtom' pwsafe.cpp:(.text+0x3872): undefined reference to XmuClientWindow'
collect2: error: ld returned 1 exit status
Makefile:624: recipe for target 'pwsafe' failed
make: *** [pwsafe] Error 1

i'm opening a .psafe3 db under ubuntu, client compiled from github sources without errors

pwsafe-cli -f ~/Dropbox/psafe_backup.psafe3 
Enter passphrase for /home/taz/Dropbox/psafe_backup.psafe3: 
Passphrase is incorrect

gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4

any idea?

Once set, it is not possible to remove the value of a field (e.g. group or notes) using the --edit command. Attempting to use an empty value results in the original value being used.

Thank you for pwsafe.

I intended using Password Gorilla as a gui and Pwsafe as a CLI but it seems pwsafe is not compatible with V3 database format.

$ pwsafe -v --list -f /tmp/Gorilla.psafe3
rng seeded with 1024 bytes from /home/adrian/.rnd
Enter passphrase for /tmp/Gorilla.psafe3:
Passphrase is incorrect
Enter passphrase for /tmp/Gorilla.psafe3:

I know users can currently dump out the database to a txt file but it would be very powerful if an export feature KeePassX XML format could be added. Below an example xml file with the minimum entries needed.

Mappings:
pwsafe = keepassx

uuid= doesn't translate
group= group>title
name= entry>title
login= entry>username
passwd= entry>password
notes= entry>comment

Example pwsafe export:

# passwordsafe version 2.0 database"
uuid    group   name    login   passwd  notes
"123d9-daf-df-3423423"  "retail"    "amazon"    "myamazonuser"  "sjfJ849"   "superfluous comment"
"4599d934-dsfs-324" "retail"    "netflix"   "netflixuser"   "dj3W$#"    ""
"4kdfkd-434-jj" "email" "gmail" "mygmail"   "dfkpass"   ""

Example xml in keepassx xml format for export:

<!DOCTYPE KEEPASSX_DATABASE>
<database>
 <group>
  <title>Internet</title>
  <entry>
   <title>github</title>
   <username>githubusername</username>
   <password>githubpassword</password>
   <comment>optional comment</comment>
  </entry>
 </group>
 <group>
  <title>retail</title>
  <entry>
   <title>amazon</title>
   <username>username</username>
   <password>myamazonpw</password>
  </entry>
 </group>
 <group>
  <title>retail</title>
  <entry>
   <title>netflix</title>
   <username>username</username>
   <password>mynfxpw</password>
  </entry>
 </group>
</database>

Building from master (9d9758f), configure detects that X11/Xmu/Atoms.h is missing, but continues. However the build then fails because this file is missing.

If the XMU library is necessary for building the configure script should fail if it detects it is missing.
If the XMU library is not necessary, pwsafe.cpp should have conditionals blocks based on HAVE_LIBXMU from config.h.

Details below.

Extract of the configure output when building on Ubuntu 16.04 (without packages libxmu-dev, libxmu-headers):

checking X11/Xlib.h usability... yes
checking X11/Xlib.h presence... yes
checking for X11/Xlib.h... yes
checking X11/Xatom.h usability... yes
checking X11/Xatom.h presence... yes
checking for X11/Xatom.h... yes
checking X11/Xmu/Atoms.h usability... no
checking X11/Xmu/Atoms.h presence... no
checking for X11/Xmu/Atoms.h... no

But the build fails:

LC_MESSAGES=C make
make  all-am
make[1]: Entering directory '/home/omengue/tmp/pwsafe'
g++ -DHAVE_CONFIG_H -I.     -g -O2 -Wall -MT pwsafe.o -MD -MP -MF .deps/pwsafe.Tpo -c -o pwsafe.o pwsafe.cpp
pwsafe.cpp:120:27: fatal error: X11/Xmu/Atoms.h: No such file or directory
compilation terminated.
Makefile:636: recipe for target 'pwsafe.o' failed
make[1]: *** [pwsafe.o] Error 1
make[1]: Leaving directory '/home/omengue/tmp/pwsafe'
Makefile:522: recipe for target 'all' failed
make: *** [all] Error 2

Greetings.

I love pwsafe and have used it regularly for years.

The only problem I have is that I cannot easily create multi-line notes. I need to use ^V ^M to create newlines in the Notes field, and if my notes should change, I have to rewrite the entire field.

it would be great if -a and -e (add and edit) would check my environment for $EDITOR and/or $VISUAL and use an editor to edit the notes. I think /dev/shm is designed for this sort of thing, a ramdisk that is entirely ephemeral.

--hymie!

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 result:

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 from Arch Linux AUR)

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

An import option that can read a standard KeePassX XML file into pwsafe would be very useful. Find an example XML in #3

Hi Nicolas, great to see you got back to maintain pwsafe! Are you planning a new release anytime soon? I'd like to see the couple of bugs you fixed make their ways into a fetchable tarball and be able to update the FreeBSD port. Thanks!

Is there a plan to make a release? I want to package this for void linux and it's easier that a proper release will be accepted (void-linux/void-packages#33470).

Otherwise, can you make release 0.2.0 available here? Either (a) tag 0.2.0 the commit 191f16b and/or (b) make the original pwsafe-0.2.0.tar.gz available here (it can be downloaded from https://web.archive.org/web/20190116040527/http://nsd.dyndns.org/pwsafe/).

Chromium needs the same paste filled twice.
See these Bugs:
https://bugs.chromium.org/p/chromium/issues/detail?id=819113
https://bugs.chromium.org/p/chromium/issues/detail?id=778686

I'd suggest a workaround: pwsafe -t -up foobar fills username and password twice.

Hi! I’m not sure if there is a better way to contact you than this. Your website here seems to be offline. This is relevant to pwsafe because that website used to carry the 0.2.0 release, which, I think, was the most recent, and does not seem to be present here on Github.