debug / fix sending web portal message so that it can be replied online

[tomholub]

• send a message from Android app through FES
• open the received link on the other account, enter password. Make sure the message opens on fes.flowcrypt.com/...
• click reply on fes.flowcrypt.com/...

1. send a message from Android app through FES - works
2. open the received link on the other account, enter password. Make sure the message opens on fes.flowcrypt.com/...- works
3. click reply on fes.flowcrypt.com/...- I don't see reply button for a message that was send from Android. But I see this button for the web realization

It seems I have bug on my side. Can we debug this case?

@tomholub Please let me know what info I should provide.

Originally posted by @DenBond7 in #1629 (comment)

@DenBond I'm filing it as a separate issue. Likely a problem with encoding of reply info div.

[tomholub]

You you could send one message from browser extension and one from android, then download back the armored message from FES for each one of them and decrypt them. Then compare the difference in the contents.

[tomholub]

Here is the infodiv content on browser:

      const infoDiv = Ui.e('div', {
        'style': 'display: none;',
        'class': 'cryptup_reply',
        'cryptup-data': Str.htmlAttrEncode({
          sender: newMsgData.from,
          recipient: Value.arr.withoutVal(Value.arr.withoutVal(recipients, newMsgData.from), this.acctEmail),
          subject: newMsgData.subject,
          token: response.replyToken,
        })
      });

Contains sender, recipient (array), subject, token. Is that what you are encoding as well? I think I've seen something else.

[DenBond7]

It's strange. I can't decrypt a message from the web version via gpg nor PGPainless

https://flowcrypt.com/RtXpbqBxr0
qwerty1234

But can decrypt a message from Android

https://fes.flowcrypt.com/message/6c13d405-c984-4175-b395-2cdbfda42c64
qwerty1234

[DenBond7]

Btw, web version and PGPainless produce a different password-protected message

PGPainless

web

To have more details I need to have not expired key for den@flowcrypt.com. Then I can provide examples for the same key

[github-actions]

There were 1 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[tomholub]

Yes, because you are comparing legacy flowcrypt.com api (browser extension) to FES API (Android).

I'll update your keys so you can do the same on your flowcrypt account on browser extension. Then you can compare.

[tomholub]

Updated your key on EAP - you should be now able to test from flowcrypt.com account on browser extension (after resetting it).

The password-encryption algorithm has changed between original flowcrypt.com/api (used on non-FES accounts on browser extension) and FES API (used for customers that run FES, plus flowcrypt.com accounts). Thus the difference.

[DenBond7]

Thank you! I will try it soon

[DenBond7]

Fixed