Skip to content

Commit 9d3f575

Browse files
committed
New release
1 parent 446e459 commit 9d3f575

9 files changed

+48
-60
lines changed

documents/License.pdf

36.9 KB
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.

examples/tools/protected_update_data_set/README.md

Lines changed: 0 additions & 60 deletions
This file was deleted.
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
1. Usage
2+
Start the "protected_update_data_generator.exe" with following options, in order to generate the data set for protected update data set.
3+
payload_version=%%d <default: 0>
4+
trust_anchor_oid=%%s <default: E0E8>
5+
target_oid=%%s <default: E0E2>
6+
offset=%%d <default: 0>
7+
write_type=%%d <default: 1>
8+
<options : Write (1), EraseAndWrite (2)>
9+
sign_algo=%%s <default: ES_256>
10+
<options : ES_256 , RSA-SSA-PKCS1-V1_5-SHA-256>
11+
priv_key=%%s <default: NULL>
12+
<note : Provide key file(pem format). Corresponding certificate containing public key should be written to trust_anchor>
13+
payload=%%s <default: NULL>
14+
<note : Provide file with path with readable content>
15+
16+
Example :
17+
18+
protected_update_data_generator.exe payload_version=3 trust_anchor=E0E8 target=E0E1 offset=01 write_type=1 sign_algo=RSA_SSA_PKCS1_V1_5_SHA_256 priv_key=<pem private key> payload=<text file with readable data>
19+
20+
a. Generate a manifest data with payload version 3, trust anchor 0xE0E3. The manifest is signed using "priv_key" and RSA_SSA_PKCS1_V1_5_SHA_256 is the signing algorithm
21+
b. Fragments of data is generated from text file provided in option "payload"
22+
b. The generated fragments is written at target OID 0xE0E1 from offset 1
23+
24+
2. Sample :
25+
A sample script demonstrating the usage of the tool is available in ..\samples
26+
27+
3. Limitations
28+
a. Only SHA-256 digest algorithm is supported for hash calculation
29+
b. Manifest version number is 1
30+
31+
4. Environment
32+
a. The availabel executable is built using microsoft visual studio 2010 in windows 10 (64 bit)
33+
b. mbedTLS 2.7.0 is used for crypto operation.
34+
c. The following MACRO must be disabled/ enabled when using mbedTLS for this tool.
35+
i. Enable :
36+
MBEDTLS_FS_IO
37+
MBEDTLS_PEM_PARSE_C
38+
MBEDTLS_BASE64_C
39+
MBEDTLS_ECDSA_DETERMINISTIC
40+
MBEDTLS_HMAC_DRBG_C
41+
MBEDTLS_ECDSA_DETERMINISTIC_DEBUG
42+
MBEDTLS_RSA_C
43+
MBEDTLS_PKCS1_V15
44+
MBEDTLS_PK_RSA_ALT_SUPPORT
45+
MBEDTLS_TIMING_C
46+
47+
ii.Disable
48+
MBEDTLS_NO_PLATFORM_ENTROPY in mbedTLS_config.h

0 commit comments

Comments
 (0)