Tulevik's KeePass 2.47 module

[Ed_P]

Ref: posting #87 Tulevik's Modules Collection - Porteus 5.01 XFCE

KeePass is a free, open source and easy-to-use password manager.

I use KeePass in Windows and have used the KeePassX module and the KeePassXC appimage in Porteus, in each case I am able to execute KeePass with the location of my kdbx file and have the opening KeePass screen requesting the file's password. With this module I am unable to do that. keepass "file's location & name" brings up a blank KeePass window where I have to search for the kdbx file each time I invoke the module's keepass app. Anyone got a fix for this problem?

Added in 52 minutes 47 seconds:
Windows' version 2.57, module version 2.47.

[Tulevik]

Ref: posting #87 Tulevik's Modules Collection - Porteus 5.01 XFCE

KeePass is a free, open source and easy-to-use password manager.

I use KeePass in Windows and have used the KeePassX module and the KeePassXC appimage in Porteus, in each case I am able to execute KeePass with the location of my kdbx file and have the opening KeePass screen requesting the file's password. With this module I am unable to do that. keepass "file's location & name" brings up a blank KeePass window where I have to search for the kdbx file each time I invoke the module's keepass app. Anyone got a fix for this problem?

Added in 52 minutes 47 seconds:
Windows' version 2.57, module version 2.47.

How strange. Did you try the other way round, i.e. creating files with this module and trying to open them with the Windows and the other version for Porteus?

[Ed_P]

I found that the 2.47 KeePass app creates a KeePass folder in the /home/guest/.config folder with an .xml file in it that retains the name and location of the last .kdbx file used and when KeePass starts a 2nd time it uses the .kdbx file referenced in the .xml file. So I made a module of the .xzm file and activate it before starting KeePass.

While the .xml file might work with the KeePassX and KeePassXC apps the folder structure wouldn't fit with Windows folders.

[Tulevik]

I found that the 2.47 KeePass app creates a KeePass folder in the /home/guest/.config folder with an .xml file in it that retains the name and location of the last .kdbx file used and when KeePass starts a 2nd time it uses the .kdbx file referenced in the .xml file. So I made a module of the .xzm file and activate it before starting KeePass.

While the .xml file might work with the KeePassX and KeePassXC apps the folder structure wouldn't fit with Windows folders.

So, would you recommend using KeePassXC &/or KeePassX instead of this one?

[Ed_P]

So, would you recommend using KeePassXC &/or KeePassX instead of this one?

No. If possible a more current version of this one would be nice. What did you use to create the module?

[Tulevik]

So, would you recommend using KeePassXC &/or KeePassX instead of this one?

No. If possible a more current version of this one would be nice. What did you use to create the module?

slapt-mod - m keepass

[Ed_P]

So the question becomes, who created the KeePass app that slapt-mod used. Will they be creating a knew one anytime soon?

[Tulevik]

So the question becomes, who created the KeePass app that slapt-mod used. Will they be creating a knew one anytime soon?

Perhaps converting an existing package from Fedora/Debian/whatever distro would give us a more recent version. I'll try it on following days, but I'm not sure about the dependencies needed.

[Ed_P]

No hurry. The current module works.

[Tulevik]

No hurry. The current module works.

That's fine, but these things really bug me. I try to publish useful things on the forum, but sometimes things go awry, being the dependecies thing the main offender .

[Ed_P]

I try to publish useful things on the forum,

And you have succeeded.

sometimes things go awry, being the dependecies thing the main offender

Dependencies are awkward in Porteus: 1. Finding them. 2. Determining how many modules with need a particular one. If a dependency is needed in 5 modules do you add it to each module or make it a module of it and note that it is needed for each of the 5 modules thus a user only needs to download it once, load it once and the 5 modules are all smaller. If it's small you include it, if it's large you make it a separate module. A goal of Porteus is keeping things small, especially modules, so module building is a challenge.

[Tulevik]

module building is a challenge.

Quite a challenge!

[i3slkiller]

I know the pain of creating Porteus modules and updating them, thus I wrote PorteusBuild scripts to make easier to maintain them. Over time these too have become harder to maintain, so I'm writing prtbuild script (who noticed this earlier?) and rewrote all PorteusBuilds to PRTBUILD files. This tool is "almost"-finished, but I am too lazy to write docs for that