Unable to decrypt document

[kybernetikos]

For the last few months, I've been using a monod document to keep my daily journal. Today, I tried to load it up and was told "We were unable to decrypt the document. Either the secret has not been supplied or it is invalid. We have redirected you to a new document."

The link I was using was a link that did include the secret, that I have inside another monod document, and it has worked consistently in the past. When it failed, I searched through my browser history to find the link as I used it in the past. It failed in the same way. I am now unable to access my journal, which is pretty distressing.

All of the links to other monod documents that I have tried continue to work.

The document is https://monod.lelab.tailordev.fr/56dc0203-5ef0-45ce-a122-75351d5de4e0#{I removed the secret since I'm posting to a public github issue}

[willdurand]

Outch. That's pretty bad 😔

Not sure what happens here to be honest.. Would you mind sharing your full link by email so that I can try to debug it? (will AT tailordev.fr)

[willdurand]

Hi @kybernetikos, which browser are you using? Also, which version if it is Chrome?

It looks like something went wrong and the decryption failed with the following error ccm: tag does not match, which means it is not possible to do anything... There are a couple reasons related to the crypto layer:

• ccm: tag doesn't match bitwiseshiftleft/sjcl#53
• CCM: Tag not computed correctly on initial call to decrypt (latest Canary) bitwiseshiftleft/sjcl#280

The last link being related to a Chrome version, which may cause such an error. It might be an explanation, but it might be something else. I reviewed the whole thing, and I don't see any reason for this to happen (yet).

I am still investigating and trying to:

1. understand what could have happened here
2. why it happened
3. how to reproduce this thing
4. how to fix this critical issue

At the time of writing, I have no clue at all. I am not aware of any similar problem, and as heavy Monod users (using our public demo instance), we've never experienced that.

I do apologize for the data you've likely lost. We have backups for 24h. Yet, if your document got corrupted for some reasons, I cannot do anything anymore. Anyway, that's pretty bad for everyone, since we don't want our users to lose their content, even if our public instance is for demo. This is the instance we use internally too 😢

If I am talking about corrupted file here, it is because I think it might be an explanation. The Monod logic is not that complicated, and the most complicated thing is the crypto layer, which we did not (re)invent. The whole thing is well covered by tests. One option would be a network error or any similar bad event that causes your document to be corrupted.