-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
After Crash Wrong Password Allowed Entry #1474
Comments
Ok, now a second time it has done this. This time the password just timed out overnight then when I mistyped the password it said "Invalid Passphrase!" but STILL opened and let me send encrypted messages. THIS IS A SERIOUS BUG. There is a possibility I typed the correct passphrase this time. It would still be a bug because it told me I typed the wrong one... |
@landry314 It would definitely help to get debug logs, I can't reproduce this at all |
"Could not grab logs from your device." |
Android devices running older OS versions like 2.3 will not be able to do the easy method of grabbing logs. Instead you might have to just enable USB debugging and run "adb logcat" from your terminal. |
wrong thread, sorry. |
Co-authored-by: alansley <[email protected]>
One time, after TextSecure crashed then I immediately reopened it, it asked me for my password, then when I entered the wrong password it still opened like I had entered the right password. I'm sure the password was wrong.
This could have been because the password was cached already even though TextSecure thought it wasn't. I don't know.
The text was updated successfully, but these errors were encountered: