You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@sadasant Can we split the above list to algorithms supported by the service vs the ones that need local implementation?
We can then log a separate issue for the former, target it sooner and keep this issue to do further investigation on the latter.
To avoid editing the description of this issue (it seemed rude to me), I made a new issue for the remote only changes: #11260, it's a copy of this one, without As many of these as possible should be supported locally without writing our own cryptography. in the description.
Since the goal is to have as many algorithms working locally as possible, I made another issue to investigate what algorithms, from all the algorithms that Key Vault Keys offer, can be implemented locally in Node 8: #11261 , and I gave it an estimate of 5.
I made another issue to implement the local algorithms in Key Vault Keys: #11262 , and I gave it an estimate of 3.
I'll close this issue and we can follow up in those three others.
For Key Vault 7.2-preview, to
EncryptionAlgorithm
(in swagger, theKeyOperationsParameters
model), add the following algorithms:As many of these as possible should be supported locally without writing our own cryptography.
Also add the following properties:
Iv
(model property:iv
)AdditionalAuthenticatedData
(model property:aad
)Tag
(model property:tag
)These will likely need to be in a new options type/parameter passed to
Encrypt
andDecrypt
.See the service version 7.1 -> 7.2-preview diff 🔒 for details.
The text was updated successfully, but these errors were encountered: