KeePass for BlackBerry v2 now available for BETA
 

If you're a user of the KeePass Password Safe on the desktop you know that their version 2 changes the database format significantly. To be compatible I've had to re-work the back end of KeePassBB to read and write the new format.

The BETA release is here: KeePass for BlackBerry v2 BETA

Notes:

KeePassBB v1 and KeePassBB v2 are 2 different programs and can be installed on the device at the same time. This is important because the 2 versions can't read each other's file formats. If you need to use both v1 and v2 database formats, you'll need both programs. It was just too complicated to have 1 program version work on both database versions.

You must have BlackBerry OS 4.5 or greater to run KeePassBB v2.

Desktop synchronization should be fully functional and can be run side-by-side with version 1 sync.

The user interface isn't changed much, if at all.

REMINDER: This is a BETA release and problems are to be expected. Make sure you have a good backup of your database file before trying this release.

Your feedback is important. Please let me know how the program's working, especially in the area of performance.

Anyone tried it yet? Need some feedback.

It works OK. Thanks!!
 

I just installed and is working well. I still maintain V1 in the phone and both are working. Let see what happen once I use everyday.

Thanks!!!!!

Remy,

There is a bug in both ver 1.2 and 2.0

I did not create keepass db on BB. It was pushed to the BB during sync. I had no issue with opening the DB on device or computer. But while synicing when I used to put the correct password in Dm it used to say:
Unable to Decrypt Device Database using the supplied credentials.

with the following in the error log:

a KeePassBB - Transaction completed. - 4/12 19:26:06
a KeePassBB - Ending transaction. - 4/12 19:26:06
a KeePassBB - Convert
com.fairview5.keepassbb.kpobjects.PwSyncManager$Pw SyncMessage ->
DataBuffer - 4/12 19:26:00
a KeePassBB - isSyncObjectDirty
com.fairview5.keepassbb.kpobjects.PwSyncManager$Pw SyncMessage:120 -
4/12 19:26:00
a KeePassBB - getSyncVersion - 4/12 19:26:00
a KeePassBB - Convert com.fairview5.keepassbb.kpobjects.PwSyncObject
-> DataBuffer - 4/12 19:26:00
a KeePassBB - Unable to decrypt device database using the supplied
credentials - 4/12 19:26:00
a KeePassBB - net.rim.device.api.crypto.CryptoIOException (
net.rim.device.api.crypto.BadPaddingException ):null - 4/12 19:26:00
S Java Exception - CryptoIOException - 4/12 19:26:00
a System - CMM: keepassbb(780) no sig from 0x33 - 4/12 19:25:54
a System - CMM: keepassbb(780) no sig from 0x33 - 4/12 19:25:54
a KeePassBB - isSyncObjectDirty
com.fairview5.keepassbb.kpobjects.PwSyncObject:100 - 4/12 19:25:54
a KeePassBB - getSyncVersion - 4/12 19:25:54
a KeePassBB - getSyncObjects PwSyncObject PwSyncMessage - 4/12 19:25:54
a KeePassBB - clearSyncObjectDirty 100 - 4/12 19:25:54
a KeePassBB - AddSyncObject
com.fairview5.keepassbb.kpobjects.PwSyncObject - 4/12 19:25:54
a KeePassBB - Convert PwSyncObject from buffer - 4/12 19:25:54
a KeePassBB - getSyncVersion - 4/12 19:25:54
a KeePassBB - clearSyncObjectDirty 130 - 4/12 19:25:54
a KeePassBB - AddSyncObject
com.fairview5.keepassbb.kpobjects.PwSyncManager$Pw SyncCredentials -
4/12 19:25:54
a KeePassBB - Convert PwSyncCredentials from buffer - 4/12 19:25:54
a KeePassBB - getSyncVersion - 4/12 19:25:54
a KeePassBB - It isn't. - 4/12 19:25:54
a KeePassBB - Checking to see if app is running... - 4/12 19:25:54

I figured out the issue after many days. The issue was the Master password that i had set. It had characters ! and #. '!' being the first character. I set a simple password and the issue was resolved.

Thanks,
Satish

Interesting problem. Let me look at it.

Wow, great catch!! I'll get a fix out over the weekend.

KeePassBB2 v 2.0 - Build 2.0.1255 - Released May 8 2009
 

KeePassBB2 v 2.0 - Build 2.0.1255 - Released May 8 2009
-------------------------------------------------------
A little history... The first version of KeePassBB stored a single database in the device's internal persistent store. This was pretty stable but had one drawback...you couldn't maintain multiple databases as some users had requested. In a subsequent release, I changed over from the internal store to using files on the device's filesystem. While this satisfied the requirement to manage multiple databases, it wreaked havoc on the synchronization process because a good portion of the device's filesystem becomes unavailable when the devices is plugged into a USB port.

So now I've come full circle. With this release of KeePassBB2, I've reverted to the internal store to recover some synchronization stability, however, I've left the ability to use the filesystem as an option but without synchronization. See the FAQ for more information about the two modes and how to switch between them.

This release also fixes a font selection bug and a bug where an "!" in a password wasn't being passed correctly between the desktop add-in and the device.

Link: KeePass for BlackBerry v2 BETA

KeePassBB2 Build 2.0.1255 Sync Problem
 

I am still having problems syncing. For testing, I made the password just the letter p.

Here is the log:

Name: CryptoIOException
GUID: 9c3cd62e3320b498
Time: May 09, 2009 14:51:55
The file could not be decrypted using the supplied credentials.
keepassbb2-1
Kdb4File
open
0x785
keepassbb2-1
Kdb4File
open
0x6DE
keepassbb2-1
Kdb4File
openInternal
0xF7F
keepassbb2-1
Kdb4Synchronizer
isSyncObjectDirty
0x3037
net_rim_os-8
SerialSyncDaemon
<private>
0x808A
net_rim_os-8
SerialSyncDaemon
<private>
0x7FC0
net_rim_os-8
SerialSyncDaemon
<private>
0x754C
net_rim_os-8
SerialSyncDaemon
<private>
0x70EC
net_rim_os-8
SerialSyncDaemon
run
0x6FCC
net_rim_cldc-1
Thread
run
0xB0C9

Thank you so much for all the work you do on this program.

Can you open the databases individually using that password? Are you using key files?

Yes, I can open the databases individually. And, no, I am not using key files.

Did you re-install the desktop addin? The add-in version should match the program version. I.E. 2.0.1255. If not, run the msi file to re-install it and try again.

Blast! :oops: I am sorry. What's worse than me making a dumb mistake? It's when that mistake causes someone else work. It works fine, when I installed it all! I knew better, just wasn't thinking.

Thank you for the help and sorry to have caused you a problem.

No worries. I meant to put a reminder in the change log but I forgot. :)

Error "Unable to Decrypt Device Database using the supplied credentials. "
 

Just just installed and cannot make the sync work. THe BB version and the desktop sync version are both .1255.

I have tried uninstalling/reinstalling the desktop, and the BB software. he behavior hasn't changed.

What seems odd is that the initial sync works well. I can delete the internal database, clear the BB keyfile and then sync from the desktop to the BB. When I set the internal key file to the file that I manually copied from the desktop to the BB I can see my information. If I change one item on the PC and try to resync the "Unable to Decrypt Device Database using the supplied credentials." pops up.

Anyone have any thoughts on what to try next?

When you sync, are you entering both the password and keyfile when prompted?

BB Sync Key Problem
 

The desktop sync software is asking me for the password and the key file. I enter the password, and then browse to the same key file that I used on the initial sync to the BB.

OK, let me investigate a bit.

Oh yeah, how many bytes are in your keyfile?

Sync Problem
 

Key file is a picture, 2.41 MB (2,532,385 bytes),

Password is 4 characters

Yikes!

File size is likely the cause
 

Tried a much smaller file, still a picture. The new key file is 54.1 KB (55,496 bytes). Sync now works.