TextSecure user, and I can verify this as accurate.<p>When I first saw the stagefright bug, I looked for a way to disable MMS in the app. There is no way to disable MMS in the app, so I had a friend MMS me a message, and I got the warning as the post describes.<p>Feel free to test it out for yourself, but it was nice to see that TextSecure, by its nature, is secure from this bug through design.
Err wow I didn't think me raising an issue on Github would put me on the frontpage of HN. But I am glad to see that they handle this well by default - another reason why I will be keeping it!
I haven't found a way to block numbers in TextSecure or I would use it<p>... Oh they implemented it last month :D <a href="https://github.com/WhisperSystems/TextSecure/issues/222" rel="nofollow">https://github.com/WhisperSystems/TextSecure/issues/222</a>
As a digital and security training for human rights defenders and journalists all over the world - this is one of the reasons why I try as hard as possible to push the awesome work of the WhisperSystems team and Moxie.
There's a tool called "Disable Service" with which you can unload app- and system daemons, including MMS processes (both in your messaging or globally on a system level): <a href="https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=en" rel="nofollow">https://play.google.com/store/apps/details?id=cn.wq.disables...</a>
See also: <a href="https://github.com/WhisperSystems/TextSecure/issues/3818" rel="nofollow">https://github.com/WhisperSystems/TextSecure/issues/3818</a>
This is a great example of where usability and security meet. Auto downloading MMS messages is certainly much nicer from a UX perspective. However it can lead to bugs as we are witnessing.<p>I think they struck a good medium.