Skip to main content

Data migration tool from Figaro's Password Manager 2

Figaro's Password Manager 2 was my favorite password management tool.
It is GTK2-application to preserve and manage your pairs of ID and password secretly with cipher.
To my regret, its Debian package was orphaned many years ago and
I thought it was time to switch to another password management tool.

But besides finding a good alternative choice, I had a big problem: migration.
Figaro's Password Manager 2 does have data export function, but only in special XML format.
If you want to move your data to a different application, you have to change the format of the data even if the application can import the data.

As my next password management tool is KeePass2 or KeePassXC, I need a XML to CSV data converter.
So, I have been developing the conversion tool very slowly and finally, completed.
Today, I published it on GitHub, which I named fpm2_csv.

The history of the code is quite embarrassing, but very few people in the world would be interested in it, that doesn't matter.

All the conversion processes are written in XSLT. During the development, I feel exciting that you can even write a process to escape double-quote, comma, and line feed characters for CSV format only with XSLT functions.

Comments

Popular posts from this blog

Configuring Network Manager for PPPoE connection

When I'm home, I use fiber-optic line with a dedicated old small router (YAMAHA RT107e) for access to the Internet. But I recently became anxious about the router. If it fails, how can I survive until I get another one? So, I tried to connect my Debian desktop PC to the fiber-optic line without the router. The PC have to talk to the other side of the line with PPPoE but I did not know how. In my PC, the Network Manager manages network configuration. So, I had to configure the Network Manager to utilize the pppoe like : nmcli connection add ifname eth0 connection.type pppoe username USERNAME password PASSWORD

Sharing one home directory between the Linux machines with the different display resolutions and different pointing devices, keeping $HOME/.config data for each machine

 Back in 1990's, it was common practice to share one home directory between many UNIX servers using NFS. But it is not in these days. But I have become to want to share my home directory between two different Linux machines: One is  a Debian GNU/Linux installed as a primary OS of a dual boot machine,  and the other is a virtualized Linux box within the Virtualbox running under the Windows 10, a secondary OS of the dual-boot. They have different display resolutions and pointing devices. These differences led me to an annoying problem: if you open GNOME desktop environment, display and pointing device setting became broken. Today's GNOME desktop environment stores most of the settings to the files under $HOME/.config directory. But if you share $HOME/.config between two machines, the stored configuration for a particular machine may become incompatible with other machines with different display resolutions and pointing devices. Indeed, my GNOME desktop has become unusable. To ove