chromium/src
0
Fork 0
Code Activity
1,428,755 Commits 3 Branches 23,233 Tags
00b861abe677c1df2e83895e6ebac39cf5c96f7a
Commit Graph

5 Commits

Author SHA1 Message Date
Avi Drissman
8ba1bad80d Update copyright headers in components/ 
The methodology used to generate this CL is documented in
https://crbug.com/1098010#c34.

No-Try: true
No-Presubmit: true
Bug: 1098010
Change-Id: If6a3370b0b2849d889ce797596fe1ccbad2f3fe6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3891619
Auto-Submit: Avi Drissman <avi@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Owners-Override: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1046502}
 2022-09-13 19:22:36 +00:00
Victor Hugo Vianna Silva
cded1c3ffa [automated] Drop needless <vector> includes in /components/gcm_driver 
This is among the most costful includes for the Chromium build.
https://commondatastorage.googleapis.com/chromium-browser-clang/include-analysis.html

This batch of CLs attempts to detect and remove leftover includes with a
heuristic: choose files which don't contain 'std::vector' or 'push_back'.
This doesn't really guarantee that std::vector is not being used, as
shown by the snippets below, so please review carefully.
```
auto v = GetVector();
MyVectorAlias v = GetVector();
my_vector_ = GetVector();
```

This CL was uploaded by git cl split.

R=fgorski@chromium.org

Bug: 1233968
Change-Id: Ia6fe9b685b7d55fd78b64860d1a58349a3fc83d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3056962
Auto-Submit: Victor Vianna <victorvianna@google.com>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Commit-Queue: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#906480}
 2021-07-29 00:23:20 +00:00
peter
81a290d32a Convert the encryption header parsers to be iterator-based. 
BUG=538576

Review-Url: https://codereview.chromium.org/1509683002
Cr-Commit-Position: refs/heads/master@{#402914}
 2016-06-29 20:01:23 +00:00
peter
471cd60ba3 Rename Encryption-Key to Crypto-Key, "key" parameter to "aesgcm128". 
Mechanical renames to align us with draft-thomson-http-encryption-02.
Beyond -02, this CL also integrates the rename from the Encryption-Key
header to Crypto-Key[1], and the "key" parameter to "aesgcm128"[2].

Note that the algorithmic changes of [1] have not been implemented yet.

[1] https://goo.gl/f9ktM0
[2] https://goo.gl/hX9g3C

BUG=486040

Review URL: https://codereview.chromium.org/1446163002

Cr-Commit-Position: refs/heads/master@{#359840}
 2015-11-16 15:22:34 +00:00
peter
1f99ff0f7c Add parsers for the Encryption and Encryption-Key HTTP headers. 
These headers are defined in the following IETF draft:
  https://tools.ietf.org/html/draft-thomson-http-encryption-01

They contain the information required to decrypt an encryption GCM
message send through either the Web Push protocol, or using the
same properties in the existing GCM protocol.

The messages will be received by the Google Cloud Messaging (GCM)
driver, either through the GCM engine (on desktop) or Google
Play Services on Android, together with these headers. The
messages then have to be decrypted before being forwarded to the
feature consumer, which will initially be Push Notifications.

BUG=486040

Review URL: https://codereview.chromium.org/1244803002

Cr-Commit-Position: refs/heads/master@{#352027}
 2015-10-02 14:21:35 +00:00