Decryption bug hunt!

Coordinator
Jul 27, 2014 at 9:57 PM
Since the release of WinKee 1.1.0.6 earlier today, we are on a warpath against bugs that prevent database decryption.

This includes introduction of mail-based error reports and a potentially rapid update schedule in situations where we decide that an update would help us track down or squish a bug.

We are really sorry for the inconvenience this might cause some users, but we decided that this is the best way to ensure all our users will have the best possible experience and reliability.

This post will be updated when error reports arrive and serve as a central tracking place for our investigation. Any and all comments and insights will help us resolve this quickly, so if you have anything to add, don't hesitate.
Coordinator
Jul 27, 2014 at 9:59 PM
Edited Jul 27, 2014 at 10:05 PM
Report 1

WinKee Exception Report
Exception type: Exception
Exception message: The file is corrupted.
Exception stack trace: at KeePassLib.Serialization.KdbxFile.Load(Stream sSource, KdbxFormat kdbFormat, IStatusLogger slLogger, CancellationToken token)
at KeePassLib.PwDatabase.Open(Stream ioSource, CompositeKey pwKey, IStatusLogger slLogger, CancellationToken token)
at WinKee.MainPage.<>c__DisplayClass5.<OpenAction>b__8()
Additional details:

Application version: 1.1.0.6

This is the first error report and as such points out that the error reporting in 1.1.0.6 was lacking in precision. We deployed 1.1.0.7 with improvements for certification immediately.
Coordinator
Jul 28, 2014 at 8:00 AM
Report 2

Exception type: InvalidOperationException
Exception message: The ReadElementContentAsString method is not supported on node type Attribute. Line 34, position 19.
Exception stack trace: at System.Xml.XmlReader.SetupReadElementContentAsXxx(String methodName)
at System.Xml.XmlReader.ReadElementContentAsString()
at KeePassLib.Serialization.KdbxFile.ReadString(XmlReader xr)
at KeePassLib.Serialization.KdbxFile.ReadProtectedBinary(XmlReader xr)
at KeePassLib.Serialization.KdbxFile.ReadXmlElement(KdbContext ctx, XmlReader xr)
at KeePassLib.Serialization.KdbxFile.ReadDocumentStreamed(XmlReader xr, Stream sParentStream, CancellationToken token)
at KeePassLib.Serialization.KdbxFile.Load(Stream sSource, KdbxFormat kdbFormat, IStatusLogger slLogger, CancellationToken token)
at KeePassLib.PwDatabase.Open(Stream ioSource, CompositeKey pwKey, IStatusLogger slLogger, CancellationToken token)
at WinKee.MainPage.<>c__DisplayClass5.<OpenAction>b__8()

This is something new and previously unseen, we are investigating right now.
Coordinator
Jul 28, 2014 at 8:51 AM
mar3ek wrote:
Report 2
This issue has been identified as a problem in the database itself - the original KeePass code struggled with reading certain elements of the database (not sure why, might be an API difference between full-blown .NET framework and its WinPho counterpart). Workaround is being implemented and tested right now and should be deployed into the store within 24 hours.
Coordinator
Jul 28, 2014 at 12:14 PM
Received another report with the exact same stack trace as the Report 2. It seems that the main problem in decrypting databases lies in protected binaries. The current workaround should be able to resolve these issues.
Coordinator
Jul 28, 2014 at 1:45 PM
We finally managed to REPLICATE the aforementioned issues on our development machines. Development of a proper fix is now underway.
Coordinator
Jul 28, 2014 at 6:08 PM
The promised bugfix has been implemented, tested and patched WinKee version (1.1.0.8) has been uploaded into the Windows Phone Store for certification. Distribution through the Store should begin within hours.
Coordinator
Jul 28, 2014 at 10:12 PM
Windows Phone Store successfully processed WinKee 1.1.0.8 and the updated version is now rolling out across markets. All users should be seeing an auto-update notification (if app auto-update is enabled on their device) in the next few hours, or check for updates manually to force an update.

The issues reported so far should be resolved by this update. If you find any more problems, please report them so we can resolve them as soon as possible.