oversecio/oversec_crypto

Oversec "Freezes" client apps (ANR) when using "invisible" encoding

Closed this issue · 3 comments

Reported to happen with Messaging (com.google.android.apps.messaging) when using "invisible encoding" with symmetric encryption,
directly after tapping the "encrypt" button.


Version: 1001001
Build-Type: release
Flavor: google
Android-Version: 23
Android-Build: Nextbit/ether/ether:6.0.1/MMB29M/00WW_1_350:user/release-keys
Hardware: Nextbit/Nextbit / Robin / ether
Open-Keychain-Version: 41010
-------------------------Client-Package: com.google.android.apps.messaging
Client-Version: 19035148

This is indeed related to the invisible characters used for the invisible encoding.

Could it be that the characters from the extended pane are causing a problem?

Not related to a particular class of invisible characters, for now the only way forward is to catch this problem, and warn the user / ask to choose another encoding with this app.

This is NOT related to invisible encoding, only to the sheer length of some (PGP encoded) messages!

And due to the fact that e.g. "Google Messenger" has a "maxLength=2000" set to the message text input field.