@@ -93,37 +93,37 @@ public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() {
93
93
* [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
94
94
* [ENCRYPT_DECRYPT][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ENCRYPT_DECRYPT].
95
95
*
96
- * Algorithms beginning with " RSA_SIGN_" are usable with
96
+ * Algorithms beginning with ` RSA_SIGN_` are usable with
97
97
* [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
98
98
* [ASYMMETRIC_SIGN][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_SIGN].
99
99
*
100
- * The fields in the name after " RSA_SIGN_" correspond to the following
100
+ * The fields in the name after ` RSA_SIGN_` correspond to the following
101
101
* parameters: padding algorithm, modulus bit length, and digest algorithm.
102
102
*
103
103
* For PSS, the salt length used is equal to the length of digest
104
104
* algorithm. For example,
105
105
* [RSA_SIGN_PSS_2048_SHA256][google.cloud.kms.v1.CryptoKeyVersion.CryptoKeyVersionAlgorithm.RSA_SIGN_PSS_2048_SHA256]
106
106
* will use PSS with a salt length of 256 bits or 32 bytes.
107
107
*
108
- * Algorithms beginning with " RSA_DECRYPT_" are usable with
108
+ * Algorithms beginning with ` RSA_DECRYPT_` are usable with
109
109
* [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
110
110
* [ASYMMETRIC_DECRYPT][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_DECRYPT].
111
111
*
112
- * The fields in the name after " RSA_DECRYPT_" correspond to the following
112
+ * The fields in the name after ` RSA_DECRYPT_` correspond to the following
113
113
* parameters: padding algorithm, modulus bit length, and digest algorithm.
114
114
*
115
- * Algorithms beginning with " EC_SIGN_" are usable with
115
+ * Algorithms beginning with ` EC_SIGN_` are usable with
116
116
* [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
117
117
* [ASYMMETRIC_SIGN][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_SIGN].
118
118
*
119
- * The fields in the name after " EC_SIGN_" correspond to the following
119
+ * The fields in the name after ` EC_SIGN_` correspond to the following
120
120
* parameters: elliptic curve, digest algorithm.
121
121
*
122
- * Algorithms beginning with " HMAC_" are usable with
122
+ * Algorithms beginning with ` HMAC_` are usable with
123
123
* [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
124
124
* [MAC][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.MAC].
125
125
*
126
- * The suffix following " HMAC_" corresponds to the hash algorithm being used
126
+ * The suffix following ` HMAC_` corresponds to the hash algorithm being used
127
127
* (eg. SHA256).
128
128
*
129
129
* For more information, see [Key purposes and algorithms]
0 commit comments