I like using KeePassx simply because it’s the first password manager I used that worked. It may not have all the bells and whistles that other managers may have but it does what I want it to do all the time, without fail. Since I’ve been the target of relentless hacking by state sponsored Gang Stalkers, I favor security apps which offer the use of keyfiles as an additional option. Now that I’ve been forced into using “Tails”, MAC Spoofing, Tor, Truecrypt and other security measures, I also favor software that is portable over a range of platforms. It really sucks that you have to go through all of these multiple layers of protecting just to send an email or post to your blog, but that is the world you get when people are sin laden and immoral.
This first step is to install KeePassX, this is best done of course, by compiling for your particular distro. I’m using Slacko Puppy version 5.7.0, released Mar 2014 and have it set up to load devx_slacko_5.7.0.sfs at boot automatically. For those who don’t yet know, devx is the compiler that is necessary to make and compile any programs for installation in Puppy. Different versions have different devx’s which can either be installed themselves as pets or, loaded separately as needed in the form of an .sfs module.
Trust me, just get the devx.sfs module for your particular version and load at boot time with SFS-Load on-the-fly, it is way too big to install and will only bog down your machine if you do. Since you rarely compile after getting your system’s initial configuration set, having devx installed is an unnecessary resource hog.
Probably the worst caveat in using a very early version of KeePass (KeePassX is the linux ported version of KeePass) is that the database’s aren’t compatible. If you make a KeePassX or KeePass database in version 1, you will have to go through “changes” to make it readable in version 2 and it will have limited functionality. I don’t believe a version 2 database is backward compatible either. This lack of functionality is most egregious when using KeePass on a phone, but why would you want to do that anyway when all phones have been hacked? If I did such a thing I would swear to you that as soon as I put my KeePassX database on my new Droid, was the first day my blog was hacked. I then had to change all of my passwords. Never again.
Bottom line? Don’t put any password management database on any mobile device save for a laptop, period. Not unless that is, you want all your security breached one awful day. Surprise!
Okay, back to KeePassX. After you have it installed, you gotta get the script that makes it portable.
Download attached archive (keepassx_portable_script.tar) and unpack it somewhere in your home directory.
Make keepassx_make_portable.sh executable and run it.
Copy the created KeePassX folder to your USB flash drive, probably to the same folder with Windows version of KeePassX.
To start program use keepassx.sh script.
In case of problems you can follow the instructions from keepassx_make_portable.sh script and copy all the needed files by hand.
- (3 KiB) Downloaded 1402 time
Now that you have the script, the fun begins with qt. In Slacko, symbolic links are used for calling libraries, for various reasons. What this means is that libraries may not be installed in the absolute paths where those scripts expect them to be. This is the problem that I ran into with the keepassx portable script.
You can upack and run the script in any directory that you like and it will find it’s way, but you have to chown +x keepassx_make_portable.sh first of course (duh). What the script will then do is use your existing installation to create a keepassx executable bin file that can access the qt libraries copied to the same folder it is in. The problem arises with the absolute path that the script looks for qt in and, the actual version number of qt itself.
The first thing you need to do is locate the absolute path were the actual qt libs are located in your distro’s filesystem. As long as you have any version of qt 4, it should be OK. Next, you need to open the script as text in an editor and replace the paths (and qt lib version names) that the script will cp to those of the actual qt lib’s you have installed. The script will then copy two qt libs and one xtml file. After you run it you can verify that the libs and xtml files are actually in the lib folder. You will immediately know upon running the script whether or not it was successful because it will be quiet and not echo any error messages. If it does complain upon execution (./keepassx.sh), then it will tell you what went wrong.
Thats about it. Now just click on the keepassx.sh and see what happens. If nothing happens then you forgot to make it executable (chown +x). You might want to add an icon image so that you can drag keepassx.sh to the desktop as a link, having the icon graphic will then allow you to pretty it up (set icon).
I had planned to include some screenshots of all the steps above as they were performed but it’s late, I’m tired and being gassed pretty heavily by the Gang Stalkers right now. At least you now have the jist of it and if you’ve bothered to read this far without drooling, then you you probably don’t need illustrations anyway (comfortable with text and the command line etc…). I tell you, I’ve got to find out what technology that they are using to accomplish this torture, but that will be for future endeavor.
P.S. I came back the next day and provided you screenshots. Your Welcome.