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.
2013-04-20 19:22:04 +00:00
|
|
|
package org.thoughtcrime.securesms.database;
|
|
|
|
|
|
|
|
|
|
public interface MmsSmsColumns {
|
|
|
|
|
|
|
|
|
|
public static final String ID = "_id";
|
|
|
|
|
public static final String NORMALIZED_DATE_SENT = "date_sent";
|
|
|
|
|
public static final String NORMALIZED_DATE_RECEIVED = "date_received";
|
|
|
|
|
public static final String THREAD_ID = "thread_id";
|
|
|
|
|
public static final String READ = "read";
|
2013-04-26 18:23:43 +00:00
|
|
|
public static final String BODY = "body";
|
2014-02-03 03:38:06 +00:00
|
|
|
public static final String ADDRESS = "address";
|
|
|
|
|
public static final String ADDRESS_DEVICE_ID = "address_device_id";
|
2014-07-25 22:14:29 +00:00
|
|
|
public static final String RECEIPT_COUNT = "delivery_receipt_count";
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
|
|
|
|
public static class Types {
|
|
|
|
|
protected static final long TOTAL_MASK = 0xFFFFFFFF;
|
|
|
|
|
|
|
|
|
|
// Base Types
|
2014-04-01 01:47:24 +00:00
|
|
|
protected static final long BASE_TYPE_MASK = 0x1F;
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
2014-04-01 01:47:24 +00:00
|
|
|
protected static final long BASE_INBOX_TYPE = 20;
|
|
|
|
|
protected static final long BASE_OUTBOX_TYPE = 21;
|
|
|
|
|
protected static final long BASE_SENDING_TYPE = 22;
|
|
|
|
|
protected static final long BASE_SENT_TYPE = 23;
|
|
|
|
|
protected static final long BASE_SENT_FAILED_TYPE = 24;
|
|
|
|
|
protected static final long BASE_PENDING_SECURE_SMS_FALLBACK = 25;
|
|
|
|
|
protected static final long BASE_PENDING_INSECURE_SMS_FALLBACK = 26;
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
|
|
|
|
protected static final long[] OUTGOING_MESSAGE_TYPES = {BASE_OUTBOX_TYPE, BASE_SENT_TYPE,
|
2014-03-01 22:17:55 +00:00
|
|
|
BASE_SENDING_TYPE, BASE_SENT_FAILED_TYPE,
|
2014-04-01 01:47:24 +00:00
|
|
|
BASE_PENDING_SECURE_SMS_FALLBACK,
|
|
|
|
|
BASE_PENDING_INSECURE_SMS_FALLBACK};
|
2014-03-01 22:17:55 +00:00
|
|
|
|
|
|
|
|
// Message attributes
|
|
|
|
|
protected static final long MESSAGE_ATTRIBUTE_MASK = 0xE0;
|
|
|
|
|
protected static final long MESSAGE_FORCE_SMS_BIT = 0x40;
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
|
|
|
|
// Key Exchange Information
|
2013-08-22 00:25:19 +00:00
|
|
|
protected static final long KEY_EXCHANGE_BIT = 0x8000;
|
|
|
|
|
protected static final long KEY_EXCHANGE_STALE_BIT = 0x4000;
|
|
|
|
|
protected static final long KEY_EXCHANGE_PROCESSED_BIT = 0x2000;
|
|
|
|
|
protected static final long KEY_EXCHANGE_CORRUPTED_BIT = 0x1000;
|
|
|
|
|
protected static final long KEY_EXCHANGE_INVALID_VERSION_BIT = 0x800;
|
2013-09-14 20:33:23 +00:00
|
|
|
protected static final long KEY_EXCHANGE_BUNDLE_BIT = 0x400;
|
2014-02-16 23:23:49 +00:00
|
|
|
protected static final long KEY_EXCHANGE_IDENTITY_UPDATE_BIT = 0x200;
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
|
|
|
|
// Secure Message Information
|
|
|
|
|
protected static final long SECURE_MESSAGE_BIT = 0x800000;
|
2014-02-19 21:46:49 +00:00
|
|
|
protected static final long END_SESSION_BIT = 0x400000;
|
2014-02-21 07:00:38 +00:00
|
|
|
protected static final long PUSH_MESSAGE_BIT = 0x200000;
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
2014-02-20 05:06:54 +00:00
|
|
|
// Group Message Information
|
2014-02-22 01:51:25 +00:00
|
|
|
protected static final long GROUP_UPDATE_BIT = 0x10000;
|
|
|
|
|
protected static final long GROUP_QUIT_BIT = 0x20000;
|
2014-02-20 05:06:54 +00:00
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
// Encrypted Storage Information
|
|
|
|
|
protected static final long ENCRYPTION_MASK = 0xFF000000;
|
|
|
|
|
protected static final long ENCRYPTION_SYMMETRIC_BIT = 0x80000000;
|
|
|
|
|
protected static final long ENCRYPTION_ASYMMETRIC_BIT = 0x40000000;
|
|
|
|
|
protected static final long ENCRYPTION_REMOTE_BIT = 0x20000000;
|
|
|
|
|
protected static final long ENCRYPTION_REMOTE_FAILED_BIT = 0x10000000;
|
|
|
|
|
protected static final long ENCRYPTION_REMOTE_NO_SESSION_BIT = 0x08000000;
|
2014-03-19 19:37:46 +00:00
|
|
|
protected static final long ENCRYPTION_REMOTE_DUPLICATE_BIT = 0x04000000;
|
2014-04-10 22:20:43 +00:00
|
|
|
protected static final long ENCRYPTION_REMOTE_LEGACY_BIT = 0x02000000;
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
|
|
|
|
public static boolean isFailedMessageType(long type) {
|
|
|
|
|
return (type & BASE_TYPE_MASK) == BASE_SENT_FAILED_TYPE;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isOutgoingMessageType(long type) {
|
|
|
|
|
for (long outgoingType : OUTGOING_MESSAGE_TYPES) {
|
|
|
|
|
if ((type & BASE_TYPE_MASK) == outgoingType)
|
|
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return false;
|
|
|
|
|
}
|
|
|
|
|
|
2014-03-01 22:17:55 +00:00
|
|
|
public static boolean isForcedSms(long type) {
|
|
|
|
|
return (type & MESSAGE_FORCE_SMS_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
public static boolean isPendingMessageType(long type) {
|
|
|
|
|
return
|
|
|
|
|
(type & BASE_TYPE_MASK) == BASE_OUTBOX_TYPE ||
|
|
|
|
|
(type & BASE_TYPE_MASK) == BASE_SENDING_TYPE;
|
|
|
|
|
}
|
|
|
|
|
|
2014-04-01 01:47:24 +00:00
|
|
|
public static boolean isPendingSmsFallbackType(long type) {
|
|
|
|
|
return (type & BASE_TYPE_MASK) == BASE_PENDING_INSECURE_SMS_FALLBACK ||
|
|
|
|
|
(type & BASE_TYPE_MASK) == BASE_PENDING_SECURE_SMS_FALLBACK;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isPendingSecureSmsFallbackType(long type) {
|
|
|
|
|
return (type & BASE_TYPE_MASK) == BASE_PENDING_SECURE_SMS_FALLBACK;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isPendingInsecureSmsFallbackType(long type) {
|
|
|
|
|
return (type & BASE_TYPE_MASK) == BASE_PENDING_INSECURE_SMS_FALLBACK;
|
2014-03-01 22:17:55 +00:00
|
|
|
}
|
|
|
|
|
|
2013-06-25 04:02:30 +00:00
|
|
|
public static boolean isInboxType(long type) {
|
|
|
|
|
return (type & BASE_TYPE_MASK) == BASE_INBOX_TYPE;
|
|
|
|
|
}
|
|
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
public static boolean isSecureType(long type) {
|
|
|
|
|
return (type & SECURE_MESSAGE_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2014-02-21 07:00:38 +00:00
|
|
|
public static boolean isPushType(long type) {
|
|
|
|
|
return (type & PUSH_MESSAGE_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2014-02-19 21:46:49 +00:00
|
|
|
public static boolean isEndSessionType(long type) {
|
|
|
|
|
return (type & END_SESSION_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
public static boolean isKeyExchangeType(long type) {
|
|
|
|
|
return (type & KEY_EXCHANGE_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isStaleKeyExchange(long type) {
|
|
|
|
|
return (type & KEY_EXCHANGE_STALE_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isProcessedKeyExchange(long type) {
|
|
|
|
|
return (type & KEY_EXCHANGE_PROCESSED_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2013-08-22 00:25:19 +00:00
|
|
|
public static boolean isCorruptedKeyExchange(long type) {
|
|
|
|
|
return (type & KEY_EXCHANGE_CORRUPTED_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isInvalidVersionKeyExchange(long type) {
|
|
|
|
|
return (type & KEY_EXCHANGE_INVALID_VERSION_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2013-09-14 20:33:23 +00:00
|
|
|
public static boolean isBundleKeyExchange(long type) {
|
|
|
|
|
return (type & KEY_EXCHANGE_BUNDLE_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2014-02-16 23:23:49 +00:00
|
|
|
public static boolean isIdentityUpdate(long type) {
|
|
|
|
|
return (type & KEY_EXCHANGE_IDENTITY_UPDATE_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2014-02-22 01:51:25 +00:00
|
|
|
public static boolean isGroupUpdate(long type) {
|
|
|
|
|
return (type & GROUP_UPDATE_BIT) != 0;
|
2014-02-20 05:06:54 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isGroupQuit(long type) {
|
|
|
|
|
return (type & GROUP_QUIT_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
public static boolean isSymmetricEncryption(long type) {
|
|
|
|
|
return (type & ENCRYPTION_SYMMETRIC_BIT) != 0;
|
|
|
|
|
}
|
2014-11-03 23:16:04 +00:00
|
|
|
|
|
|
|
|
public static boolean isAsymmetricEncryption(long type) {
|
|
|
|
|
return (type & ENCRYPTION_ASYMMETRIC_BIT) != 0;
|
|
|
|
|
}
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
|
|
|
|
public static boolean isFailedDecryptType(long type) {
|
|
|
|
|
return (type & ENCRYPTION_REMOTE_FAILED_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2014-03-19 19:37:46 +00:00
|
|
|
public static boolean isDuplicateMessageType(long type) {
|
|
|
|
|
return (type & ENCRYPTION_REMOTE_DUPLICATE_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
public static boolean isDecryptInProgressType(long type) {
|
|
|
|
|
return
|
|
|
|
|
(type & ENCRYPTION_REMOTE_BIT) != 0 ||
|
|
|
|
|
(type & ENCRYPTION_ASYMMETRIC_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
public static boolean isNoRemoteSessionType(long type) {
|
|
|
|
|
return (type & ENCRYPTION_REMOTE_NO_SESSION_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
2014-04-10 22:20:43 +00:00
|
|
|
public static boolean isLegacyType(long type) {
|
|
|
|
|
return (type & ENCRYPTION_REMOTE_LEGACY_BIT) != 0;
|
|
|
|
|
}
|
|
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
public static long translateFromSystemBaseType(long theirType) {
|
|
|
|
|
// public static final int NONE_TYPE = 0;
|
|
|
|
|
// public static final int INBOX_TYPE = 1;
|
|
|
|
|
// public static final int SENT_TYPE = 2;
|
|
|
|
|
// public static final int SENT_PENDING = 4;
|
|
|
|
|
// public static final int FAILED_TYPE = 5;
|
|
|
|
|
|
|
|
|
|
switch ((int)theirType) {
|
|
|
|
|
case 1: return BASE_INBOX_TYPE;
|
|
|
|
|
case 2: return BASE_SENT_TYPE;
|
|
|
|
|
case 4: return BASE_OUTBOX_TYPE;
|
|
|
|
|
case 5: return BASE_SENT_FAILED_TYPE;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return BASE_INBOX_TYPE;
|
|
|
|
|
}
|
|
|
|
|
|
2013-06-25 04:02:30 +00:00
|
|
|
public static int translateToSystemBaseType(long type) {
|
|
|
|
|
if (isInboxType(type)) return 1;
|
|
|
|
|
else if (isOutgoingMessageType(type)) return 2;
|
|
|
|
|
else if (isFailedMessageType(type)) return 5;
|
|
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
|
}
|
|
|
|
|
|
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.
2013-04-20 19:22:04 +00:00
|
|
|
|
|
|
|
|
//
|
|
|
|
|
//
|
|
|
|
|
//
|
|
|
|
|
// public static final int NONE_TYPE = 0;
|
|
|
|
|
// public static final int INBOX_TYPE = 1;
|
|
|
|
|
// public static final int SENT_TYPE = 2;
|
|
|
|
|
// public static final int SENT_PENDING = 4;
|
|
|
|
|
// public static final int FAILED_TYPE = 5;
|
|
|
|
|
//
|
|
|
|
|
// public static final int OUTBOX_TYPE = 43; // Messages are stored local encrypted and need delivery.
|
|
|
|
|
//
|
|
|
|
|
//
|
|
|
|
|
// public static final int ENCRYPTING_TYPE = 42; // Messages are stored local encrypted and need async encryption and delivery.
|
|
|
|
|
// public static final int SECURE_SENT_TYPE = 44; // Messages were sent with async encryption.
|
|
|
|
|
// public static final int SECURE_RECEIVED_TYPE = 45; // Messages were received with async decryption.
|
|
|
|
|
// public static final int FAILED_DECRYPT_TYPE = 46; // Messages were received with async encryption and failed to decrypt.
|
|
|
|
|
// public static final int DECRYPTING_TYPE = 47; // Messages are in the process of being asymmetricaly decrypted.
|
|
|
|
|
// public static final int NO_SESSION_TYPE = 48; // Messages were received with async encryption but there is no session yet.
|
|
|
|
|
//
|
|
|
|
|
// public static final int OUTGOING_KEY_EXCHANGE_TYPE = 49;
|
|
|
|
|
// public static final int INCOMING_KEY_EXCHANGE_TYPE = 50;
|
|
|
|
|
// public static final int STALE_KEY_EXCHANGE_TYPE = 51;
|
|
|
|
|
// public static final int PROCESSED_KEY_EXCHANGE_TYPE = 52;
|
|
|
|
|
//
|
|
|
|
|
// public static final int[] OUTGOING_MESSAGE_TYPES = {SENT_TYPE, SENT_PENDING, ENCRYPTING_TYPE,
|
|
|
|
|
// OUTBOX_TYPE, SECURE_SENT_TYPE,
|
|
|
|
|
// FAILED_TYPE, OUTGOING_KEY_EXCHANGE_TYPE};
|
|
|
|
|
//
|
|
|
|
|
// public static boolean isFailedMessageType(long type) {
|
|
|
|
|
// return type == FAILED_TYPE;
|
|
|
|
|
// }
|
|
|
|
|
//
|
|
|
|
|
// public static boolean isOutgoingMessageType(long type) {
|
|
|
|
|
// for (int outgoingType : OUTGOING_MESSAGE_TYPES) {
|
|
|
|
|
// if (type == outgoingType)
|
|
|
|
|
// return true;
|
|
|
|
|
// }
|
|
|
|
|
//
|
|
|
|
|
// return false;
|
|
|
|
|
// }
|
|
|
|
|
//
|
|
|
|
|
// public static boolean isPendingMessageType(long type) {
|
|
|
|
|
// return type == SENT_PENDING || type == ENCRYPTING_TYPE || type == OUTBOX_TYPE;
|
|
|
|
|
// }
|
|
|
|
|
//
|
|
|
|
|
// public static boolean isSecureType(long type) {
|
|
|
|
|
// return
|
|
|
|
|
// type == SECURE_SENT_TYPE || type == ENCRYPTING_TYPE ||
|
|
|
|
|
// type == SECURE_RECEIVED_TYPE || type == DECRYPTING_TYPE;
|
|
|
|
|
// }
|
|
|
|
|
//
|
|
|
|
|
// public static boolean isKeyExchangeType(long type) {
|
|
|
|
|
// return type == OUTGOING_KEY_EXCHANGE_TYPE || type == INCOMING_KEY_EXCHANGE_TYPE;
|
|
|
|
|
// }
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
}
|