You are not logged in.
Pages: 1
I'd like to add the keepass repository to get the latest version. I'm on the stretch version of Bunsenlabs and the ppa details are here:
https://launchpad.net/~jtaylor/+archive/ubuntu/keepass
I can't figure out how to add it. Keepass is v2.35 on Bunsenlabs but I'd like to have the latest 2.37 version of keepass. Any ideas how to go about this?
Offline
Using ubuntu ppa's in debian is a surefire way to break everything, no matter what people that build software for ubuntu say.
Is there something critical that you can do on 2.37 that you can't do on 2.35?
Offline
Furthermore this PPA is nothing Ubuntu-official but by some random guy (though he's in Ubuntu's packaging team). Not sure if I would trust him with such a crucial thing like a password manager...
Nevertheless for using PPAs the way as described on the PPA's page you have to install software-properties-common and python-software-properties.
Edit: don't do that ever. Even if you're sure to know what you're doing. Future failures can't be foreseen.
Last edited by vinzv (2018-04-09 21:23:34)
Offline
Edit: never mind. Didn't look carefully enough at the post.
Last edited by kozimodo (2018-04-09 15:02:45)
Offline
What about the community fork, KeepassXC, which came in first in the recent Linux Format magazine shootout of password managers? I backported it to the Jessie-based MX 15 test repo: https://repology.org/metapackage/keepassxc/versions, so I know it's possible. I seem to remember that it needed a few extra backports first, so let me check if I have an OBS repo for that already set up; I sort of remember that I did...yeah, set one up ten months ago, back when it was version 2.2.0: https://build.opensuse.org/package/show … /keepassxc
so I'll see about updating it to the current 2.3.1.
Though I also built keepass2 2.38 for MX 15 back in Jan: http://mxrepo.com/mx/testrepo/pool/test/k/keepass2/
Edit: and I added it to the keepassXC repo: https://build.opensuse.org/package/show … c/keepass2
Last edited by stevep (2018-04-09 22:09:01)
Offline
Yeah, I guess I just want to be up to date but probably OK if I'm 2 or 3 revisions out. Can I use the deb in that MXRepo then? I'm on Stretch, not Jessie.
Last edited by usuallymatt (2018-04-09 20:51:04)
Offline
for using PPAs the way as described on the PPA's page you have to install software-properties-common and python-software-properties.
That actually won't work in BunsenLabs.
Which is a good thing because PPAs can wreck the system completely.
Offline
vinzv wrote:for using PPAs the way as described on the PPA's page you have to install software-properties-common and python-software-properties.
That actually won't work in BunsenLabs.
Yes, one needs to edit the respective sources.list file. But of course you're right, shouldn't have encouraged such thing. Sorry!
Offline
Yeah, I guess I just want to be up to date but probably OK if I'm 2 or 3 revisions out. Can I use the deb in that MXRepo then? I'm on Stretch, not Jessie.
You can use the one that's now in the OBS. I know that the KeepassXC 2.3.1 for Jessie needed several other updated packages, such as libsodium, libgcrypt20, libzxcvbn (where did they get that name, eh?), so it's not just a matter of getting the deb and installing it. That one's better if you enable my repo. But I'm pretty sure that the new keepass2 doesn't need any other package updates.
Oh, wait, you're on Stretch. That also needed some backports for keepassXC, but not as many. The keepass2 deb doesn't need any.
Last edited by stevep (2018-04-09 22:16:32)
Offline
I have been looking for some time at what password managers were available and eventually went for the standard Unix one, Pass, https://www.passwordstore.org/ simple, can use it in terminal and/or loads of front end options,I am using QtPass, https://qtpass.org/ imports from most other managers and for me using i3 also has a dmenu option.
Last edited by titan (2018-04-13 16:15:37)
Offline
For pass you will have to migrate your password store. It can be done but should be kept in mind when deciding to switch.
Offline
Is it OK to stay with an older (0.4.4) keepassx?
As far as I can see, in Helium there are keepassx v.2.03-1 and keepassx2 v.2.35+dfsg-2 (whatever it means).
I somehow dislike the new version, so I built the older one from sources from its site (I hope):
#!/bin/bash
# install_old_keepassx.sh
sudo apt-get install qt4-qmake
sudo apt-get install qt4-dev-tools qt4-designer
sudo apt-get install g++
sudo apt-get install libxtst-dev
SRC_VER=0.4.4
SRC_NAME=keepassx-$SRC_VER
SRC_FILE=${SRC_NAME}.tar.gz
SRC_ADDR=https://www.keepassx.org/releases/${SRC_VER}/${SRC_FILE}
pushd /tmp
wget $SRC_ADDR
tar zxvf $SRC_FILE
cd $SRC_NAME
# FIX it:
# lib/random.cpp:98:19: error: ‘getpid’ was not declared in this scope
# To fix this problem open src/lib/random.cpp and add:
# #include <unistd.h>
sed -i '/#include "random.h"/a #include <unistd.h>' src/lib/random.cpp
qmake-qt4
make
sudo checkinstall
popd
Offline
It's up to you, really. Just know that if you use an older version of software with the explicit intent to protect passwords, you won't be getting any security updates, which is a bit sketchy.
Offline
^ +1
Also, check the changelog, some bugs have been fixed in the new versions:
Offline
Pages: 1