session-android

Commit Graph

Author	SHA1	Message	Date
Moxie Marlinspike	a601c56af1	Collapse SessionRecord, SessionState, and PreKeyRecord interfaces.	10 years ago
Moxie Marlinspike	d902c12941	Break core ratchet out into libaxolotol. 1) Break the core cryptography functions out into libaxolotol. 2) The objective for this code is a Java library that isn't dependent on any Android functions. However, while the code has been separated from any Android functionality, it is still an 'android library project' because of the JNI.	10 years ago
Moxie Marlinspike	926d3c929f	Handle simultaneous initiate protocol case. 1) Modify SessionRecord to store a list of "previous" sessions in addition to the current active session. Previous sessions can be used for receiving messages, but not for sending messages. 2) When a possible "simultaneous initiate" is detected, push the current session onto the "previous session" stack instead of clearing it and starting over. 3) Additionally, mark the new session created on a received possible "simultaneous initiate" as stale for sending. The next outgoing message would trigger a full prekey refresh. 4) Work to do: outgoing messages on the SMS transport should probably not use the existing session if it's marked stale for sending. These messages need to fail and notify the user, similar to how we'll handle SMS fallback to push users before a prekey session is created.	10 years ago
Moxie Marlinspike	a6e1d56cde	Refactor group messaging protocol. // FREEBIE	11 years ago
Moxie Marlinspike	19dddd7adf	Support for an 'end session' protocol message. 1) On the push side, this message is a flag in PushMessageContent. Any secure message with that flag will terminate the current sessin. 2) On the SMS side, there is an "end session" wire type and the convention that a message with this wire type must be secure and contain the string "TERMINATE."	11 years ago
Moxie Marlinspike	3999171377	Introduce registration-time ID for detecting stale sessions. 1) At registration time, a client generates a random ID and transmits to the the server. 2) The server provides that registration ID to any client that requests a prekey. 3) Clients include that registration ID in any PreKeyWhisperMessage. 4) Clients include that registration ID in their sendMessage API call to the server. 5) The server verifies that the registration ID included in an API call is the same as the current registration ID for the destination device. Otherwise, it notifies the sender that their session is stale.	11 years ago
Moxie Marlinspike	9438973eac	Switch to protobuf enums for push signal type.	11 years ago
Moxie Marlinspike	0ace469d74	Support for multi-device. 1) In addition to the Recipient interface, there is now RecipientDevice. A Recipient can have multiple corresponding RecipientDevices. All addressing is done to a Recipient, but crypto sessions and transport delivery are done to RecipientDevice. 2) The Push transport handles the discovery and session setup of additional Recipient devices. 3) Some internal rejiggering of Groups.	11 years ago
Moxie Marlinspike	49daa45dca	wip	11 years ago
Moxie Marlinspike	327ee4ff62	Remove unnecessary classes, up prekey limit to 100	11 years ago
Moxie Marlinspike	44092a3eff	Support for Axolotl protocol. 1) Split code into v1 and v2 message paths. 2) Do the Axolotl protocol for v2. 3) Switch all v2 entities to protobuf.	11 years ago
Moxie Marlinspike	fa5ccc3f8a	Support for server federation.	11 years ago
Moxie Marlinspike	0dd36c64a4	Basic support for encrypted push-based attachments. 1) Move the attachment structures into the encrypted message body. 2) Encrypt attachments with symmetric keys transmitted in the encryptd attachment pointer structure. 3) Correctly handle asynchronous decryption and categorization of encrypted push messages. TODO: Correct notification process and network/interruption retries.	11 years ago
Moxie Marlinspike	0cc5837d7f	Support encrypted transport, properly handle multiple recipients. 1) Add encryption support for the transport layer. This obscures metadata from the push messaging provider. 2) Better support the direction multiple destination messages is headed (one unique message per recipient).	11 years ago
Moxie Marlinspike	499de2d2bf	Move prekey jsonifcation into the push code, add identity key.	11 years ago
Moxie Marlinspike	b8f663b69c	Move common crypto classes into TextSecureLibrary. 1) Move all the crypto classes from securesms.crypto. 2) Move all the crypto storage from securesms.database.keys 3) Replace the old imported BC code with spongycastle.	11 years ago

16 Commits (544f06451fad9c4f2a711271949d917e51f9287f)