Skip to content

Issue 1622 send encrypted msg through fes - #1629

Merged
DenBond7 merged 21 commits into
masterfrom
issue_1622_send_encrypted_msg_through_fes
Jan 6, 2022
Merged

Issue 1622 send encrypted msg through fes#1629
DenBond7 merged 21 commits into
masterfrom
issue_1622_send_encrypted_msg_through_fes

Conversation

@DenBond7

@DenBond7DenBond7 commented Dec 30, 2021

Copy link
Copy Markdown
Collaborator

This PR added send encrypted msg through FES functionality.

close#1622


Tests(delete all except exactly one):

  • Difficult to test (explain why). It relates to background tasks. Tested manually.

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

  • addresses the issue it closes (if any)
  • code is readable and understandable
  • is accompanied with tests, or tests are not needed
  • is free of vulnerabilities

@DenBond7
DenBond7 marked this pull request as ready for review January 3, 2022 11:55
@DenBond7
DenBond7 requested a review from tomholubJanuary 3, 2022 11:55

@IvanPizhenkoIvanPizhenko left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to apply some changes, which simplify code

Comment threadFlowCrypt/src/main/java/com/flowcrypt/email/api/email/EmailUtil.kt Outdated
Comment threadFlowCrypt/src/main/java/com/flowcrypt/email/util/GeneralUtil.kt Outdated

@tomholubtomholub left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you tested that also replying back from FES to such a message works smoothly?

@DenBond7

Copy link
Copy Markdown
CollaboratorAuthor

Have you tested that also replying back from FES to such a message works smoothly?

Do you mean check I it works or not at all?

I was able to send a new message, reply and forward with attachments.

But for that need to add a few temporary changes. Would you like to test that?

@tomholub

tomholub commented Jan 4, 2022

Copy link
Copy Markdown
Collaborator

Have you tested that also replying back from FES to such a message works smoothly?

Do you mean check I it works or not at all?

I was able to send a new message, reply and forward with attachments.

But for that need to add a few temporary changes. Would you like to test that?

I'd like you to test this scenario manually - make sure it works:

  1. send a message from Android app through FES
  2. open the received link on the other account, enter password. Make sure the message opens on fes.flowcrypt.com/...
  3. click reply on fes.flowcrypt.com/...
  4. compose a reply on the web page and send it back
  5. make sure you receive the reply back in the android app

@DenBond7

Copy link
Copy Markdown
CollaboratorAuthor

@tomholub

I'd like you to test this scenario manually - make sure it works:

I'm trying to find a way do that. My private key for den@flowcrypt.com is expired since Jan 1

@DenBond7

Copy link
Copy Markdown
CollaboratorAuthor
  • 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.

@DenBond7

Copy link
Copy Markdown
CollaboratorAuthor

I've added changes. @tomholub, @IvanPizhenko Please re-review

@tomholub

Copy link
Copy Markdown
Collaborator

Difficult to test (explain why). It relates to background tasks. Tested manually.

We should file an issue to write test for this later. The functionality is not simple, and therefore easy to break during refactors or other development. Plus a customer relies on this. Having a test will help ensure it doesn't break.

@tomholubtomholub left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you - it's improving - please see comments.

@IvanPizhenkoIvanPizhenko left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am ok with last changes (to the my extent of understanding of this PR). However @tomholub seems to have more comments, so let him approve and merge this PR when he is also ok.

@IvanPizhenko

Copy link
Copy Markdown
Contributor

or I should also approve because I was requesting changes?

@tomholub

Copy link
Copy Markdown
Collaborator

Good question, I guess once it's ready I can force-merge it as an admin.

@DenBond7

Copy link
Copy Markdown
CollaboratorAuthor

However @tomholub seems to have more comments, so let him approve and merge this PR when he is also ok.

Good question, I guess once it's ready I can force-merge it as an admin.

I have enaugth permission to merge it as an admin. Anyway, I will do it only after @tomholub approving. It's important architecture/security issue.

@DenBond7

Copy link
Copy Markdown
CollaboratorAuthor

@tomholub Can I already merge it?

@tomholub

Copy link
Copy Markdown
Collaborator

yup

@DenBond7
DenBond7 merged commit 0ca82f8 into masterJan 6, 2022
@DenBond7
DenBond7 deleted the issue_1622_send_encrypted_msg_through_fes branch January 6, 2022 11:07
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

send password-protected message through FES and update email format

3 participants

@DenBond7@tomholub@IvanPizhenko