9 Commits (d7070e7ecf50b41c7bd8a04596716914009031ff)

Author	SHA1	Message	Date
Moxie Marlinspike	d7070e7ecf	Inserted the Registration activity into initial setup flow. ... 1) Added push messaging toggle to preferences. 2) Added push messaging registration screen to setup flow. 3) Migrated rest of SharedPreferences accessors to TextSecurePreferences.	11 years ago
Moxie Marlinspike	c2b809c7c6	Fix for long multipart message bug on some ROMs.	12 years ago
Moxie Marlinspike	b0216e1494	Finish KitKat compatibility details. ... 1) The system does actually enforce having a BROADCAST_SMS permission on the SMS receiver. Break out the "delivered" parts of this into a separate Receiver, so the permission won't trip up GB devices. 2) The system does actually enforce having "quick response" intents. Add a no-op for now. 3) Add a "make default" prompt. 4) Update settings to reflect what's going on in KitKat.	12 years ago
Desiree Sacher	4f49216103	corrected class info of NullPointerException messages	12 years ago
Desiree Sacher	ed4c8cd799	extended log of encrypted and plaintext messages NullPointerException	12 years ago
Moxie Marlinspike	7090ca4a42	Don't remote-encrypt key exchange messages	12 years ago
Moxie Marlinspike	2305a648fb	Minor refactoring	12 years ago
Moxie Marlinspike	e80882b83b	Locally encrypted messages no longer show as ciphertext notifications.	12 years ago
Moxie Marlinspike	83e260436b	Major storage layer refactoring to set the stage for clean GCM. ... 1) We now try to hand out cursors at a minimum. There has always been a fairly clean insertion layer that handles encrypting message bodies, but the process of decrypting message bodies has always been less than ideal. Here we introduce a "Reader" interface that will decrypt message bodies when appropriate and return objects that encapsulate record state. No more MessageDisplayHelper. The MmsSmsDatabase interface is also more sane. 2) We finally rid ourselves of the technical debt associated with TextSecure's initial usage of the default SMS DB. In that world, we weren't able to use anything other than the default "Inbox, Outbox, Sent" types to describe a message, and had to overload the message content itself with a set of local "prefixes" to describe what it was (encrypted, asymetric encrypted, remote encrypted, a key exchange, procssed key exchange), and so on. This includes a major schema update that transforms the "type" field into a bitmask that describes everything that used to be encoded in a prefix, and prefixes have been completely eliminated from the system. No more Prefix.java 3) Refactoring of the MultipartMessageHandler code. It's less of a mess, and hopefully more clear as to what's going on. The next step is to remove what we can from SmsTransportDetails and genericize that interface for a GCM equivalent.	12 years ago