@@ -39,24 +39,14 @@ public class CustomCodeSigning implements Serializable {
3939
4040 /**
4141 * <p>
42- * The hash algorithm used to code sign the file. You can use a string as
43- * the algorithm name if the target over-the-air (OTA) update devices are
44- * able to verify the signature that was generated using the same signature
45- * algorithm. For example, FreeRTOS uses <code>SHA256</code> or
46- * <code>SHA1</code>, so you can pass either of them based on which was used
47- * for generating the signature.
42+ * The hash algorithm used to code sign the file.
4843 * </p>
4944 */
5045 private String hashAlgorithm ;
5146
5247 /**
5348 * <p>
54- * The signature algorithm used to code sign the file. You can use a string
55- * as the algorithm name if the target over-the-air (OTA) update devices are
56- * able to verify the signature that was generated using the same signature
57- * algorithm. For example, FreeRTOS uses <code>ECDSA</code> or
58- * <code>RSA</code>, so you can pass either of them based on which was used
59- * for generating the signature.
49+ * The signature algorithm used to code sign the file.
6050 * </p>
6151 */
6252 private String signatureAlgorithm ;
@@ -153,22 +143,11 @@ public CustomCodeSigning withCertificateChain(CodeSigningCertificateChain certif
153143
154144 /**
155145 * <p>
156- * The hash algorithm used to code sign the file. You can use a string as
157- * the algorithm name if the target over-the-air (OTA) update devices are
158- * able to verify the signature that was generated using the same signature
159- * algorithm. For example, FreeRTOS uses <code>SHA256</code> or
160- * <code>SHA1</code>, so you can pass either of them based on which was used
161- * for generating the signature.
146+ * The hash algorithm used to code sign the file.
162147 * </p>
163148 *
164149 * @return <p>
165- * The hash algorithm used to code sign the file. You can use a
166- * string as the algorithm name if the target over-the-air (OTA)
167- * update devices are able to verify the signature that was
168- * generated using the same signature algorithm. For example,
169- * FreeRTOS uses <code>SHA256</code> or <code>SHA1</code>, so you
170- * can pass either of them based on which was used for generating
171- * the signature.
150+ * The hash algorithm used to code sign the file.
172151 * </p>
173152 */
174153 public String getHashAlgorithm () {
@@ -177,22 +156,11 @@ public String getHashAlgorithm() {
177156
178157 /**
179158 * <p>
180- * The hash algorithm used to code sign the file. You can use a string as
181- * the algorithm name if the target over-the-air (OTA) update devices are
182- * able to verify the signature that was generated using the same signature
183- * algorithm. For example, FreeRTOS uses <code>SHA256</code> or
184- * <code>SHA1</code>, so you can pass either of them based on which was used
185- * for generating the signature.
159+ * The hash algorithm used to code sign the file.
186160 * </p>
187161 *
188162 * @param hashAlgorithm <p>
189- * The hash algorithm used to code sign the file. You can use a
190- * string as the algorithm name if the target over-the-air (OTA)
191- * update devices are able to verify the signature that was
192- * generated using the same signature algorithm. For example,
193- * FreeRTOS uses <code>SHA256</code> or <code>SHA1</code>, so you
194- * can pass either of them based on which was used for generating
195- * the signature.
163+ * The hash algorithm used to code sign the file.
196164 * </p>
197165 */
198166 public void setHashAlgorithm (String hashAlgorithm ) {
@@ -201,25 +169,14 @@ public void setHashAlgorithm(String hashAlgorithm) {
201169
202170 /**
203171 * <p>
204- * The hash algorithm used to code sign the file. You can use a string as
205- * the algorithm name if the target over-the-air (OTA) update devices are
206- * able to verify the signature that was generated using the same signature
207- * algorithm. For example, FreeRTOS uses <code>SHA256</code> or
208- * <code>SHA1</code>, so you can pass either of them based on which was used
209- * for generating the signature.
172+ * The hash algorithm used to code sign the file.
210173 * </p>
211174 * <p>
212175 * Returns a reference to this object so that method calls can be chained
213176 * together.
214177 *
215178 * @param hashAlgorithm <p>
216- * The hash algorithm used to code sign the file. You can use a
217- * string as the algorithm name if the target over-the-air (OTA)
218- * update devices are able to verify the signature that was
219- * generated using the same signature algorithm. For example,
220- * FreeRTOS uses <code>SHA256</code> or <code>SHA1</code>, so you
221- * can pass either of them based on which was used for generating
222- * the signature.
179+ * The hash algorithm used to code sign the file.
223180 * </p>
224181 * @return A reference to this updated object so that method calls can be
225182 * chained together.
@@ -231,22 +188,11 @@ public CustomCodeSigning withHashAlgorithm(String hashAlgorithm) {
231188
232189 /**
233190 * <p>
234- * The signature algorithm used to code sign the file. You can use a string
235- * as the algorithm name if the target over-the-air (OTA) update devices are
236- * able to verify the signature that was generated using the same signature
237- * algorithm. For example, FreeRTOS uses <code>ECDSA</code> or
238- * <code>RSA</code>, so you can pass either of them based on which was used
239- * for generating the signature.
191+ * The signature algorithm used to code sign the file.
240192 * </p>
241193 *
242194 * @return <p>
243- * The signature algorithm used to code sign the file. You can use a
244- * string as the algorithm name if the target over-the-air (OTA)
245- * update devices are able to verify the signature that was
246- * generated using the same signature algorithm. For example,
247- * FreeRTOS uses <code>ECDSA</code> or <code>RSA</code>, so you can
248- * pass either of them based on which was used for generating the
249- * signature.
195+ * The signature algorithm used to code sign the file.
250196 * </p>
251197 */
252198 public String getSignatureAlgorithm () {
@@ -255,22 +201,11 @@ public String getSignatureAlgorithm() {
255201
256202 /**
257203 * <p>
258- * The signature algorithm used to code sign the file. You can use a string
259- * as the algorithm name if the target over-the-air (OTA) update devices are
260- * able to verify the signature that was generated using the same signature
261- * algorithm. For example, FreeRTOS uses <code>ECDSA</code> or
262- * <code>RSA</code>, so you can pass either of them based on which was used
263- * for generating the signature.
204+ * The signature algorithm used to code sign the file.
264205 * </p>
265206 *
266207 * @param signatureAlgorithm <p>
267- * The signature algorithm used to code sign the file. You can
268- * use a string as the algorithm name if the target over-the-air
269- * (OTA) update devices are able to verify the signature that was
270- * generated using the same signature algorithm. For example,
271- * FreeRTOS uses <code>ECDSA</code> or <code>RSA</code>, so you
272- * can pass either of them based on which was used for generating
273- * the signature.
208+ * The signature algorithm used to code sign the file.
274209 * </p>
275210 */
276211 public void setSignatureAlgorithm (String signatureAlgorithm ) {
@@ -279,25 +214,14 @@ public void setSignatureAlgorithm(String signatureAlgorithm) {
279214
280215 /**
281216 * <p>
282- * The signature algorithm used to code sign the file. You can use a string
283- * as the algorithm name if the target over-the-air (OTA) update devices are
284- * able to verify the signature that was generated using the same signature
285- * algorithm. For example, FreeRTOS uses <code>ECDSA</code> or
286- * <code>RSA</code>, so you can pass either of them based on which was used
287- * for generating the signature.
217+ * The signature algorithm used to code sign the file.
288218 * </p>
289219 * <p>
290220 * Returns a reference to this object so that method calls can be chained
291221 * together.
292222 *
293223 * @param signatureAlgorithm <p>
294- * The signature algorithm used to code sign the file. You can
295- * use a string as the algorithm name if the target over-the-air
296- * (OTA) update devices are able to verify the signature that was
297- * generated using the same signature algorithm. For example,
298- * FreeRTOS uses <code>ECDSA</code> or <code>RSA</code>, so you
299- * can pass either of them based on which was used for generating
300- * the signature.
224+ * The signature algorithm used to code sign the file.
301225 * </p>
302226 * @return A reference to this updated object so that method calls can be
303227 * chained together.
0 commit comments