Cannot browse to open databases

[Danny O'Brian]

Hi,

When trying to open a key database from the open database command in the file menu I can't select any of the databases I have created. They are greyed out.

I am using the latest KeypassX distribution on osx 10.4.7 on a macBook Pro.

Any suggestions?

[Jeff Sauer]

Try giving it an extension of .kdb... Also, from the finder, right click the .kdb file and select Open With... and specify keepassx as the default application.

[Sgf]

I have the same problem with a Powerbook (ppc) I can't open the database, I try with .kdb .pwm .xml extension and nothing works. Keepassx doesn't recongnoce it.

[imac User]

On an intel iMac. Created a new database and saved it. Now when I try to open it from keypass its greyed out. I changed the extension to be kdb. Had no effect. Tried to change the file associations for kdb, but the kepassX application is greyed out.

[Rallo]

Hi, I have the same problem, so I wrote a small shell script:

#! /bin/sh
/Applications/Home/KeePassX.app/Contents/MacOS/keepass password.kbd

First you take the application directory of KeepassX.app: /Applications/Home/KeePassX.app/

then the file you want open e.g. password.kbd

save the file as shell script e.g. password.kbd.open.sh, in same directory as password.kbd

for automaticly opening of shell skript files I use the shell Launcher Application and make a file association to .sh files, this app you can find under
http://www.maths.mq.edu.au/~steffen/tcltk/Launcher/

Now you are able to start the password.kbd file. I know its just a quick and dirty solution, but works [/url]

[ssd]

Try giving it an extension of .kdb...

Ok, that worked for me, but still, I'd consider this a bug.
If it requires the filename to end in .kdb, then it should append that to the filename if it isn't already there during saving. Or at least give a visual que somewhere that to hint that .kdb should be in the name.

Also, rather than give me a long list of greyed out filenames I can't open, it would be nice if it just didn't displayed them, and maybe had a "all files" button to show the rest and allow them to be loaded even without the extension.

[fpc]

This did work previously. Now under OSX 10.4.10 it seems to just give you the Error: The following error occured while opening the database: Decryption failed. They key is wrong or the file is damaged.

No matter how you try to select the KDB file, even my back up files which worked before cannot be opening.

[fpc]

This is a definite 100% bug under Mac OSX 10.4.10 and probably other versions.

Keepassx will no longer accept your database, say the file is corrupt, it will even stop displaying the the .kdb files as supported databases when you try to browse for your database.

FIX (Sad that Mac users need a windows Fix): Install Keepass on a windows computer, load your .kdb file from your Mac that is said to be corrupt. This should work, the Mac KeepassX incorrectly reports files as corrupt when in fact they are just fine. Go to File > Export > Keepass Database. This will ask you to keep or change the key, you can just go ahead and keep it. Then save the new database as a new file name, copy it to your Mac and then KeePassX will recognize it.

I had to completely re-install my OS to figure this out. With a fresh install of 10.4.10 and the only application running KeepassX, I knew the software was broken. The developer of the software simply said his is a corrupt file and that was the end of it. I told him a CD file does not change and would not be corrupt. He refuses to accept a bug in his software. Sure its GNU, but I mean, this is keeping peoples passwords, its not some simple app for nothing. Either support your software, charge people some $ or give up the project. Don't release buggy code which could cost people time, $ and especially their security.

[jwq]

If it requires the filename to end in .kdb, then it should append that to the filename if it isn't already there during saving.
[Edited]
Also, rather than give me a long list of greyed out filenames I can't open, it would be nice if it just didn't displayed them, and maybe had a "all files" button to show the rest and allow them to be loaded even without the extension.

I was just about to write exactly this, when I found that someone had written it already. After finding this post, I can now open KeePassX databases.

I'm still unable to import KWallet files, despite putting an ".xml" extension on the file - the file is greyed out in the open dialog. So I can't import from the test KWallet format file I made in my text editor (see <http://keepassx.sourceforge.net/forum/viewtopic.php?t=110>).

Some help with this from the devs would be appreciated.

[rodney]

I am running OS 10.4.10 on a MacBook.

I came to post about the same problem (inability to open my KeepassX file from my backup), when I saw this thread.

Adding the kdb extension AND setting KeepassX as the default application for kdb files is definitely working for me. I can open the files by double clicking, and I can open the files from the File menu of KeepassX.

At one point, Mac OS was reporting the file as a Unix executable, and warned me against opening with KeepassX. I persisted, it opened fine, and it seems to be good.

Personally - I appreciate this port of Keepass very much - and I understand that a 0.n.n version number means that there are going to be bugs! If it was a big developer, we would call them "security features"! If you don't like it, you don't have to use it....

Cheers,

Rodney

[mrYong]

This is a definite 100% bug under Mac OSX 10.4.10 and probably other versions.

Keepassx will no longer accept your database, say the file is corrupt, it will even stop displaying the the .kdb files as supported databases when you try to browse for your database.

FIX (Sad that Mac users need a windows Fix): Install Keepass on a windows computer, load your .kdb file from your Mac that is said to be corrupt. This should work, the Mac KeepassX incorrectly reports files as corrupt when in fact they are just fine. Go to File > Export > Keepass Database. This will ask you to keep or change the key, you can just go ahead and keep it. Then save the new database as a new file name, copy it to your Mac and then KeePassX will recognize it.

I had to completely re-install my OS to figure this out. With a fresh install of 10.4.10 and the only application running KeepassX, I knew the software was broken. The developer of the software simply said his is a corrupt file and that was the end of it. I told him a CD file does not change and would not be corrupt. He refuses to accept a bug in his software. Sure its GNU, but I mean, this is keeping peoples passwords, its not some simple app for nothing. Either support your software, charge people some $ or give up the project. Don't release buggy code which could cost people time, $ and especially their security.

This tip is definitely WORKS. Thank you very much fpc. You really save my life.

[dillo]

I'm still unable to import KWallet files, despite putting an ".xml" extension on the file - the file is greyed out in the open dialog. So I can't import from the test KWallet format file I made in my text editor (see <http://keepassx.sourceforge.net/forum/viewtopic.php?t=110>).

I was finally able to transfer my KeePass database from my PC to KeePassX on my Mac.

The trick is to get all of your KeePass databases synchronized on one PC (this is relatively easy to do with KeePass on the PC), and then select File -> Export To -> KeePass Database. The default suggested filename is Database.kdb.kdb. Accept the default filename and move the file created to your Mac.

On your Mac, start KeePassX, then select File -> Open Database and select the file Database.kdb.kdb. KeePassX will ask you for the passphrase. Type the passphrase, and voila, KeePassX will now display the imported PC database.

You will need to save the file to the default location for KeePassX by using File -> Save Database As dialog.

The only problem I can think of is that one cannot easily merge the existing Mac database with the one imported from the PC.

At least I am happy that I can use the PC database on my Mac, but it would be really nice if we could merge the databases.