2019-11-21 16:19:22 +00:00
|
|
|
package protocol
|
2019-07-26 07:17:29 +00:00
|
|
|
|
|
|
|
import (
|
|
|
|
"crypto/ecdsa"
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
"encoding/json"
|
2019-07-26 07:17:29 +00:00
|
|
|
"log"
|
2020-07-22 14:54:24 +00:00
|
|
|
"reflect"
|
2019-07-26 07:17:29 +00:00
|
|
|
|
|
|
|
"github.com/golang/protobuf/proto"
|
|
|
|
"github.com/jinzhu/copier"
|
2019-09-26 07:01:17 +00:00
|
|
|
"github.com/pkg/errors"
|
2020-01-02 09:10:19 +00:00
|
|
|
|
2019-11-23 17:57:05 +00:00
|
|
|
"github.com/status-im/status-go/eth-node/crypto"
|
|
|
|
"github.com/status-im/status-go/eth-node/types"
|
2019-11-21 16:19:22 +00:00
|
|
|
"github.com/status-im/status-go/protocol/encryption"
|
2020-07-31 12:22:05 +00:00
|
|
|
"github.com/status-im/status-go/protocol/encryption/multidevice"
|
|
|
|
"github.com/status-im/status-go/protocol/encryption/sharedsecret"
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
"github.com/status-im/status-go/protocol/protobuf"
|
2019-07-26 07:17:29 +00:00
|
|
|
)
|
|
|
|
|
2019-11-06 16:23:11 +00:00
|
|
|
type StatusMessageT int
|
|
|
|
|
2019-07-26 07:17:29 +00:00
|
|
|
// StatusMessage is any Status Protocol message.
|
|
|
|
type StatusMessage struct {
|
2019-09-26 07:01:17 +00:00
|
|
|
// TransportMessage is the parsed message received from the transport layer, i.e the input
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
TransportMessage *types.Message `json:"transportMessage"`
|
2019-12-02 15:34:05 +00:00
|
|
|
// Type is the type of application message contained
|
|
|
|
Type protobuf.ApplicationMetadataMessage_Type `json:"-"`
|
2019-07-26 07:17:29 +00:00
|
|
|
// ParsedMessage is the parsed message by the application layer, i.e the output
|
2020-07-27 10:13:22 +00:00
|
|
|
ParsedMessage *reflect.Value `json:"-"`
|
2019-07-26 07:17:29 +00:00
|
|
|
|
|
|
|
// TransportPayload is the payload as received from the transport layer
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
TransportPayload []byte `json:"-"`
|
2019-07-26 07:17:29 +00:00
|
|
|
// DecryptedPayload is the payload after having been processed by the encryption layer
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
DecryptedPayload []byte `json:"decryptedPayload"`
|
2020-11-18 09:16:51 +00:00
|
|
|
// UnwrappedPayload is the payload after having been unwrapped from the applicaition metadata layer
|
|
|
|
UnwrappedPayload []byte `json:"unwrappedPayload"`
|
2019-07-26 07:17:29 +00:00
|
|
|
|
|
|
|
// ID is the canonical ID of the message
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
ID types.HexBytes `json:"id"`
|
2019-07-26 07:17:29 +00:00
|
|
|
// Hash is the transport layer hash
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
Hash []byte `json:"-"`
|
2019-07-26 07:17:29 +00:00
|
|
|
|
2020-07-03 10:08:47 +00:00
|
|
|
// Dst is the targeted public key
|
|
|
|
Dst *ecdsa.PublicKey
|
|
|
|
|
2019-07-26 07:17:29 +00:00
|
|
|
// TransportLayerSigPubKey contains the public key provided by the transport layer
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
TransportLayerSigPubKey *ecdsa.PublicKey `json:"-"`
|
2019-07-26 07:17:29 +00:00
|
|
|
// ApplicationMetadataLayerPubKey contains the public key provided by the application metadata layer
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
ApplicationMetadataLayerSigPubKey *ecdsa.PublicKey `json:"-"`
|
2020-07-31 12:22:05 +00:00
|
|
|
|
|
|
|
// Installations is the new installations returned by the encryption layer
|
|
|
|
Installations []*multidevice.Installation
|
|
|
|
// SharedSecret is the shared secret returned by the encryption layer
|
|
|
|
SharedSecrets []*sharedsecret.Secret
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// Temporary JSON marshaling for those messages that are not yet processed
|
|
|
|
// by the go code
|
|
|
|
func (m *StatusMessage) MarshalJSON() ([]byte, error) {
|
|
|
|
item := struct {
|
|
|
|
ID types.HexBytes `json:"id"`
|
|
|
|
Payload string `json:"payload"`
|
|
|
|
From types.HexBytes `json:"from"`
|
|
|
|
Timestamp uint32 `json:"timestamp"`
|
|
|
|
}{
|
|
|
|
ID: m.ID,
|
2020-11-18 09:16:51 +00:00
|
|
|
Payload: string(m.UnwrappedPayload),
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
Timestamp: m.TransportMessage.Timestamp,
|
|
|
|
From: m.TransportMessage.Sig,
|
|
|
|
}
|
|
|
|
return json.Marshal(item)
|
2019-07-26 07:17:29 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// SigPubKey returns the most important signature, from the application layer to transport
|
2019-11-23 17:57:05 +00:00
|
|
|
func (m *StatusMessage) SigPubKey() *ecdsa.PublicKey {
|
|
|
|
if m.ApplicationMetadataLayerSigPubKey != nil {
|
|
|
|
return m.ApplicationMetadataLayerSigPubKey
|
2019-07-26 07:17:29 +00:00
|
|
|
}
|
|
|
|
|
2019-11-23 17:57:05 +00:00
|
|
|
return m.TransportLayerSigPubKey
|
2019-07-26 07:17:29 +00:00
|
|
|
}
|
|
|
|
|
2019-11-23 17:57:05 +00:00
|
|
|
func (m *StatusMessage) Clone() (*StatusMessage, error) {
|
2019-07-26 07:17:29 +00:00
|
|
|
copy := &StatusMessage{}
|
|
|
|
|
2019-11-23 17:57:05 +00:00
|
|
|
err := copier.Copy(©, m)
|
2019-07-26 07:17:29 +00:00
|
|
|
return copy, err
|
|
|
|
}
|
|
|
|
|
2019-11-23 17:57:05 +00:00
|
|
|
func (m *StatusMessage) HandleTransport(shhMessage *types.Message) error {
|
2019-07-26 07:17:29 +00:00
|
|
|
publicKey, err := crypto.UnmarshalPubkey(shhMessage.Sig)
|
|
|
|
if err != nil {
|
|
|
|
return errors.Wrap(err, "failed to get signature")
|
|
|
|
}
|
|
|
|
|
|
|
|
m.TransportMessage = shhMessage
|
|
|
|
m.Hash = shhMessage.Hash
|
|
|
|
m.TransportLayerSigPubKey = publicKey
|
|
|
|
m.TransportPayload = shhMessage.Payload
|
|
|
|
|
2020-07-03 10:08:47 +00:00
|
|
|
if shhMessage.Dst != nil {
|
|
|
|
publicKey, err := crypto.UnmarshalPubkey(shhMessage.Dst)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
m.Dst = publicKey
|
|
|
|
}
|
|
|
|
|
2019-07-26 07:17:29 +00:00
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2020-07-21 15:41:10 +00:00
|
|
|
func (m *StatusMessage) HandleEncryption(myKey *ecdsa.PrivateKey, senderKey *ecdsa.PublicKey, enc *encryption.Protocol, skipNegotiation bool) error {
|
2019-07-26 07:17:29 +00:00
|
|
|
// As we handle non-encrypted messages, we make sure that DecryptPayload
|
|
|
|
// is set regardless of whether this step is successful
|
|
|
|
m.DecryptedPayload = m.TransportPayload
|
2020-07-21 15:41:10 +00:00
|
|
|
// Nothing to do
|
|
|
|
if skipNegotiation {
|
|
|
|
return nil
|
|
|
|
}
|
2019-07-26 07:17:29 +00:00
|
|
|
|
|
|
|
var protocolMessage encryption.ProtocolMessage
|
|
|
|
err := proto.Unmarshal(m.TransportPayload, &protocolMessage)
|
|
|
|
if err != nil {
|
|
|
|
return errors.Wrap(err, "failed to unmarshal ProtocolMessage")
|
|
|
|
}
|
|
|
|
|
2020-07-31 12:22:05 +00:00
|
|
|
response, err := enc.HandleMessage(
|
2019-07-26 07:17:29 +00:00
|
|
|
myKey,
|
|
|
|
senderKey,
|
|
|
|
&protocolMessage,
|
|
|
|
m.Hash,
|
|
|
|
)
|
|
|
|
|
|
|
|
if err != nil {
|
|
|
|
return errors.Wrap(err, "failed to handle Encryption message")
|
|
|
|
}
|
|
|
|
|
2020-07-31 12:22:05 +00:00
|
|
|
m.DecryptedPayload = response.DecryptedMessage
|
|
|
|
m.Installations = response.Installations
|
|
|
|
m.SharedSecrets = response.SharedSecrets
|
2019-07-26 07:17:29 +00:00
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *StatusMessage) HandleApplicationMetadata() error {
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
message, err := protobuf.Unmarshal(m.DecryptedPayload)
|
2019-07-26 07:17:29 +00:00
|
|
|
if err != nil {
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
return err
|
2019-07-26 07:17:29 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
recoveredKey, err := message.RecoverKey()
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
m.ApplicationMetadataLayerSigPubKey = recoveredKey
|
2019-08-27 12:04:15 +00:00
|
|
|
// Calculate ID using the wrapped record
|
|
|
|
m.ID = MessageID(recoveredKey, m.DecryptedPayload)
|
2020-11-18 09:16:51 +00:00
|
|
|
m.UnwrappedPayload = message.Payload
|
2019-12-02 15:34:05 +00:00
|
|
|
m.Type = message.Type
|
2019-07-26 07:17:29 +00:00
|
|
|
return nil
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *StatusMessage) HandleApplication() error {
|
2019-12-02 15:34:05 +00:00
|
|
|
switch m.Type {
|
|
|
|
case protobuf.ApplicationMetadataMessage_CHAT_MESSAGE:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.ChatMessage))
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
|
2019-12-02 15:34:05 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_MEMBERSHIP_UPDATE_MESSAGE:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.MembershipUpdateMessage))
|
2019-12-02 15:34:05 +00:00
|
|
|
|
2020-01-10 18:59:01 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_ACCEPT_REQUEST_ADDRESS_FOR_TRANSACTION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.AcceptRequestAddressForTransaction))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_SEND_TRANSACTION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.SendTransaction))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_REQUEST_TRANSACTION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.RequestTransaction))
|
2019-12-02 15:34:05 +00:00
|
|
|
|
2020-01-10 18:59:01 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_DECLINE_REQUEST_ADDRESS_FOR_TRANSACTION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.DeclineRequestAddressForTransaction))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_DECLINE_REQUEST_TRANSACTION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.DeclineRequestTransaction))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_REQUEST_ADDRESS_FOR_TRANSACTION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.RequestAddressForTransaction))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_CONTACT_UPDATE:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.ContactUpdate))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
2021-05-14 21:22:50 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_PIN_MESSAGE:
|
|
|
|
return m.unmarshalProtobufData(new(protobuf.PinMessage))
|
|
|
|
|
2020-01-10 18:59:01 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_SYNC_INSTALLATION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.SyncInstallation))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_SYNC_INSTALLATION_CONTACT:
|
|
|
|
log.Printf("Sync installation contact")
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.SyncInstallationContact))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_SYNC_INSTALLATION_PUBLIC_CHAT:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.SyncInstallationPublicChat))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_SYNC_INSTALLATION_ACCOUNT:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.SyncInstallationAccount))
|
2020-01-10 18:59:01 +00:00
|
|
|
|
|
|
|
case protobuf.ApplicationMetadataMessage_PAIR_INSTALLATION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.PairInstallation))
|
2020-07-03 08:26:35 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_CONTACT_CODE_ADVERTISEMENT:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.ContactCodeAdvertisement))
|
2020-07-03 08:26:35 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_PUSH_NOTIFICATION_REQUEST:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.PushNotificationRequest))
|
2020-07-03 08:26:35 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_PUSH_NOTIFICATION_REGISTRATION_RESPONSE:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.PushNotificationRegistrationResponse))
|
2020-07-03 08:26:35 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_PUSH_NOTIFICATION_QUERY:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.PushNotificationQuery))
|
2020-07-03 08:26:35 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_PUSH_NOTIFICATION_QUERY_RESPONSE:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.PushNotificationQueryResponse))
|
2020-07-03 08:26:35 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_PUSH_NOTIFICATION_RESPONSE:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.PushNotificationResponse))
|
2020-07-22 12:59:53 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_EMOJI_REACTION:
|
2020-07-22 14:54:24 +00:00
|
|
|
return m.unmarshalProtobufData(new(protobuf.EmojiReaction))
|
2020-08-07 13:49:37 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_GROUP_CHAT_INVITATION:
|
|
|
|
return m.unmarshalProtobufData(new(protobuf.GroupChatInvitation))
|
2020-11-18 09:16:51 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_COMMUNITY_DESCRIPTION:
|
|
|
|
return m.unmarshalProtobufData(new(protobuf.CommunityDescription))
|
|
|
|
case protobuf.ApplicationMetadataMessage_COMMUNITY_INVITATION:
|
|
|
|
return m.unmarshalProtobufData(new(protobuf.CommunityInvitation))
|
2021-01-11 10:32:51 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_COMMUNITY_REQUEST_TO_JOIN:
|
|
|
|
return m.unmarshalProtobufData(new(protobuf.CommunityRequestToJoin))
|
2021-06-07 08:31:27 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_EDIT_MESSAGE:
|
|
|
|
return m.unmarshalProtobufData(new(protobuf.EditMessage))
|
2020-07-22 14:54:24 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_PUSH_NOTIFICATION_REGISTRATION:
|
|
|
|
// This message is a bit different as it's encrypted, so we pass it straight through
|
2020-11-18 09:16:51 +00:00
|
|
|
v := reflect.ValueOf(m.UnwrappedPayload)
|
2020-07-27 10:13:22 +00:00
|
|
|
m.ParsedMessage = &v
|
2020-07-22 14:54:24 +00:00
|
|
|
return nil
|
2020-12-02 14:21:26 +00:00
|
|
|
case protobuf.ApplicationMetadataMessage_CHAT_IDENTITY:
|
|
|
|
return m.unmarshalProtobufData(new(protobuf.ChatIdentity))
|
2020-01-10 18:59:01 +00:00
|
|
|
}
|
2019-07-26 07:17:29 +00:00
|
|
|
return nil
|
|
|
|
}
|
2020-07-22 14:54:24 +00:00
|
|
|
|
|
|
|
func (m *StatusMessage) unmarshalProtobufData(pb proto.Message) error {
|
|
|
|
var ptr proto.Message
|
|
|
|
rv := reflect.ValueOf(pb)
|
|
|
|
if rv.Kind() == reflect.Ptr {
|
|
|
|
ptr = pb
|
|
|
|
} else {
|
|
|
|
ptr = rv.Addr().Interface().(proto.Message)
|
|
|
|
}
|
|
|
|
|
2020-11-18 09:16:51 +00:00
|
|
|
err := proto.Unmarshal(m.UnwrappedPayload, ptr)
|
2020-07-22 14:54:24 +00:00
|
|
|
if err != nil {
|
|
|
|
m.ParsedMessage = nil
|
|
|
|
log.Printf("[message::DecodeMessage] could not decode %T: %#x, err: %v", pb, m.Hash, err.Error())
|
|
|
|
} else {
|
|
|
|
rv = reflect.ValueOf(ptr)
|
2020-07-27 10:13:22 +00:00
|
|
|
elem := rv.Elem()
|
|
|
|
m.ParsedMessage = &elem
|
2020-07-22 14:54:24 +00:00
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|