pfn/keepasshttp — Issue #33: BUG Notification: Exception "key is not a valid size"
Author: jschontzler
Created: 2011-11-15 16:38:32+00:00
State: open

I'm running on Win7. I have KeePass 2.17 installed and KeePassHttp 1.0.4.0 plug-in working.
Running FireFox 8.0, I have current PassIFox and Hostname in Titlebar plug-ins installed.
Running Chrome , I have current ChromeIPass v1.0.6 plug-in installed.

All has been working great the last couple days since I installed. Then this morning I get a ***BUG*** pop-up notification every time I open my browser to a login screen that I have a KeePass entry for.

KeePassHttp
***BUG***
System.Security.Cryptography.CryptographicException:
Specified key is not a valid size for this algorithm.
at
System.Security.Cryptography.SymmetricAlgorithm.set_
Key(Byte[ ]value)
at
System.Security.Cryptography.AesManaged.set_Key(Byte
[ ]

I couldn't cut/paste so I took screen capture to a jpg. I don't know how to post here but can email. Instead I tried to type exactly above - hopefully w/out typos.

The only thing I can think of is that accessed my kdbx file using miniKeePass on my iPhone - no problem there. I added a test entry on the iPhone app and then forwarded a copy via DropBox which of course overwrites the kdbx file in the cloud.

This is the same DropBox resident kdbx file that KeePass running on my PC is accessing. Wondering if keys got messed up in the transfer from PC -> iPhone or iPhone -> DropBox.

In KeePass, I moved the 2 old keys into the Notes section. Each shows as an 80 character string. Does that seem okay?

In an attempt to fix I deleted the FF and Chrome keys. At first Chrome complained but after a little time, on the second try it let me establish a new connection. Then FF, too.

All is back to normal now logging in just fine with the new keys. Just wondering how to avoid this in the future.

Thank you