summaryrefslogtreecommitdiffstats
path: root/components/gcm_driver/common/gcm_messages.h
diff options
context:
space:
mode:
authorpeter <peter@chromium.org>2015-10-09 03:18:52 -0700
committerCommit bot <commit-bot@chromium.org>2015-10-09 10:19:37 +0000
commitadd31f6fb477348d2b6a755cc8b6107a7fcb5339 (patch)
tree836e2bbe1c1591e260cfc3a35158acbb14d3c939 /components/gcm_driver/common/gcm_messages.h
parentdaae8f2139bd5681ff0bfbf620a86b645934cd34 (diff)
downloadchromium_src-add31f6fb477348d2b6a755cc8b6107a7fcb5339.zip
chromium_src-add31f6fb477348d2b6a755cc8b6107a7fcb5339.tar.gz
chromium_src-add31f6fb477348d2b6a755cc8b6107a7fcb5339.tar.bz2
Teach the GCM Driver how to decrypt incoming messages.
This CL teaches the GCM Driver how it can decrypt incoming messages according to draft-thomson-webpush-encryption-01 and draft-thomson-http-encryption-01. Only the Web Push protocol is supported, decryption for messages sent through the regular GCM protocol will be supported later. While this makes end-to-end encryption work, we do *not* enable this functionality by default yet, pending resolution of some ongoing discussions with the IETF and W3C Push working groups. BUG=486040 Review URL: https://codereview.chromium.org/1243563002 Cr-Commit-Position: refs/heads/master@{#353256}
Diffstat (limited to 'components/gcm_driver/common/gcm_messages.h')
-rw-r--r--components/gcm_driver/common/gcm_messages.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/components/gcm_driver/common/gcm_messages.h b/components/gcm_driver/common/gcm_messages.h
index 8d8c5b9..a6a071c 100644
--- a/components/gcm_driver/common/gcm_messages.h
+++ b/components/gcm_driver/common/gcm_messages.h
@@ -38,6 +38,10 @@ struct GCM_DRIVER_EXPORT IncomingMessage {
std::string collapse_key;
std::string sender_id;
std::string raw_data;
+
+ // Whether the contents of the message have been decrypted, and are
+ // available in |raw_data|.
+ bool decrypted;
};
} // namespace gcm