Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Password-protected messages compliance #5878

Closed
sosnovsky opened this issue Dec 5, 2024 · 2 comments · Fixed by #5879
Closed

Password-protected messages compliance #5878

sosnovsky opened this issue Dec 5, 2024 · 2 comments · Fixed by #5879

Comments

@sosnovsky
Copy link
Collaborator

sosnovsky commented Dec 5, 2024

To ensure password-protected messages comply with security rules, client apps must check the subjects of composed password-protected email messages for specified strings. If any configured terms are found, the application should display an error message indicating that the password encryption method is incompatible with the composed message.

Client configuration will have 2 new optional properties (subject check should be performed only if both properties are set):

  • disallow_password_messages_for_terms (string[]) - specifies an array of strings to check against the subject of the composed password-protected message. If any string in this array is found in the subject, an error alert must be displayed.
  • disallow_password_messages_error_text (string) - defines the text to be displayed in the error alert.

related FlowCrypt/flowcrypt-ios#2644

@sosnovsky
Copy link
Collaborator Author

sosnovsky commented Dec 5, 2024

Hi @ioanmo226, can you please work on this one next, thanks!
After implementing it in the browser extension, the same functionality should be added to iOS app (FlowCrypt/flowcrypt-ios#2644)

@ioanmo226
Copy link
Collaborator

Okay, Sure

sosnovsky pushed a commit that referenced this issue Dec 11, 2024
* feat: password protected messages compliance

* feat: added link support

* feat: target blank

* fix: term match

* fix: pr reviews
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants