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
Copy file name to clipboardExpand all lines: docs/Signing.md
+14-22Lines changed: 14 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,39 +4,18 @@
4
4
server) environment to manage wolfBoot private keys and sign the initial
5
5
firmware and all the updates for the target.
6
6
7
-
## C or Python
8
-
9
-
The tools are distributed in two versions, using the same command line syntax,
10
-
for portability reasons.
11
-
12
-
By default, C keytools are compiled. The makefiles and scripts in this
13
-
repository will use the C tools.
14
-
15
-
### C Key Tools
7
+
## C Key Tools
16
8
17
9
A standalone C version of the key tools is available in: `./tools/keytools`.
18
10
19
11
These can be built in `tools/keytools` using `make` or from the wolfBoot root using `make keytools`.
20
12
21
-
If the C version of the key tools exists they will be used by wolfBoot's makefile and scripts.
22
-
23
13
#### Windows Visual Studio
24
14
25
15
Use the `wolfBootSignTool.vcxproj` Visual Studio project to build the `sign.exe` and `keygen.exe` tools for use on Windows.
26
16
27
17
If you see any error about missing `target.h` this is a generated file based on your .config using the make process. It is needed for `WOLFBOOT_SECTOR_SIZE` used in delta updates.
28
18
29
-
### Python key tools
30
-
31
-
**Please note that the Python tools are deprecated and will be removed in future versions.**
32
-
33
-
In order to use the python key tools, ensure that the `wolfcrypt` package is
34
-
installed in your python environment. In most systems it's sufficient to run a
0 commit comments