Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1169)

Side by Side Diff: chrome/common/extensions/api/easy_unlock_private.idl

Issue 518643002: Add ability to pass decryption key id to CreateSecureMessage method (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: . Created 6 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 // Copyright 2014 The Chromium Authors. All rights reserved. 1 // Copyright 2014 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 // <code>chrome.easyUnlockPrivate</code> API that provides hooks to Chrome to 5 // <code>chrome.easyUnlockPrivate</code> API that provides hooks to Chrome to
6 // be used by Easy Unlock component app. 6 // be used by Easy Unlock component app.
7 [nodoc] namespace easyUnlockPrivate { 7 [nodoc] namespace easyUnlockPrivate {
8 // Signature algorithms supported by the crypto library methods used by 8 // Signature algorithms supported by the crypto library methods used by
9 // Easy Unlock. 9 // Easy Unlock.
10 enum SignatureType { 10 enum SignatureType {
(...skipping 59 matching lines...) Expand 10 before | Expand all | Expand 10 after
70 dictionary CreateSecureMessageOptions { 70 dictionary CreateSecureMessageOptions {
71 // Data associated with the message. The data will not be sent with the 71 // Data associated with the message. The data will not be sent with the
72 // message, but the message recepient will use the same data on its side 72 // message, but the message recepient will use the same data on its side
73 // to verify the message. 73 // to verify the message.
74 ArrayBuffer? associatedData; 74 ArrayBuffer? associatedData;
75 75
76 // Metadata to be added to the message header. 76 // Metadata to be added to the message header.
77 ArrayBuffer? publicMetadata; 77 ArrayBuffer? publicMetadata;
78 78
79 // Verification key id added to the message header. Should be set if the 79 // Verification key id added to the message header. Should be set if the
80 // message is signed using |ECDSA_P256_SHA256|. It's used by the message 80 // message is signed using |ECDSA_P256_SHA256|. Used by the message
81 // recepient to determine which key should be used to verify the message 81 // recepient to determine which key should be used to verify the message
82 // signature. 82 // signature.
83 ArrayBuffer? verificationKeyId; 83 ArrayBuffer? verificationKeyId;
84 84
85 // Decryption key id added to the message header. Used by the message
86 // recepient to determine which key should be used to decrypt the message.
87 ArrayBuffer? decryptionKeyId;
88
85 // The encryption algorithm that should be used to encrypt the message. 89 // The encryption algorithm that should be used to encrypt the message.
86 // Should not be set for a cleartext message. 90 // Should not be set for a cleartext message.
87 EncryptionType? encryptType; 91 EncryptionType? encryptType;
88 92
89 // The algorithm to be used to sign the message. 93 // The algorithm to be used to sign the message.
90 // Defaults to |HMAC_SHA256|. |ECDSA_P256_SHA256| can currently be used 94 // Defaults to |HMAC_SHA256|. |ECDSA_P256_SHA256| can currently be used
91 // only with cleartext messages. 95 // only with cleartext messages.
92 SignatureType? signType; 96 SignatureType? signType;
93 }; 97 };
94 98
(...skipping 155 matching lines...) Expand 10 before | Expand all | Expand 10 after
250 // Saves the remote device list. 254 // Saves the remote device list.
251 // |devices|: The list of remote devices to be saved. 255 // |devices|: The list of remote devices to be saved.
252 // |callback|: Called to indicate success or failure. 256 // |callback|: Called to indicate success or failure.
253 static void setRemoteDevices(Device[] devices, 257 static void setRemoteDevices(Device[] devices,
254 optional EmptyCallback callback); 258 optional EmptyCallback callback);
255 259
256 // Gets the remote device list. 260 // Gets the remote device list.
257 static void getRemoteDevices(GetRemoteDevicesCallback callback); 261 static void getRemoteDevices(GetRemoteDevicesCallback callback);
258 }; 262 };
259 }; 263 };
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698