Skip to content

Commit f9075e3

Browse files
authored
Merge pull request #111 from reubenmiller/chore-update-snapshot-1.5.1
chore: update doc snapshot for 1.5.1
2 parents a40b718 + 13d52a6 commit f9075e3

File tree

5 files changed

+84
-3
lines changed

5 files changed

+84
-3
lines changed
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
1.5.1
1+
1.5.1-4-ga215f89a5d main

versioned_docs/version-1.5.1/references/certificate-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,11 +82,11 @@ the device generating a one-time password that is communicated by the operator t
8282
whilst the device keeps trying to download its certificate.
8383
:::
8484

85-
For a guide on how to register the device, please checkout the [Connecting to Cumulocity](../../../operate/c8y/connect) guide.
85+
For a guide on how to register the device, please checkout the [Connecting to Cumulocity](../../operate/c8y/connect) guide.
8686

8787
### Using Device Management UI
8888

89-
For instructions on how to register a device using the Cumulocity Device Management UI, please see the [Connecting to Cumulocity](../../../operate/c8y/connect) guide.
89+
For instructions on how to register a device using the Cumulocity Device Management UI, please see the [Connecting to Cumulocity](../../operate/c8y/connect) guide.
9090

9191
### Using CLI Commands
9292

versioned_docs/version-1.5.1/references/hsm-support.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,34 @@ to private key stored in the HSM (a step that depends on the actual key).
3232
This feature has the following related configuration options:
3333

3434
```sh command="tedge config list --doc device.cryptoki" title="tedge config list --doc device.cryptoki"
35+
device.cryptoki.mode Whether to use a Hardware Security Module for authenticating the MQTT connection with the cloud. "off" to not use the HSM, "module" to use the provided cryptoki dynamic module, "socket" to access the HSM via tedge-p11-server signing service.
36+
Examples: off, module, socket
37+
38+
device.cryptoki.module_path A path to the PKCS#11 module used for interaction with the HSM. Needs to be set when `device.cryptoki.mode` is set to `module`.
39+
Example: /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
40+
41+
device.cryptoki.pin Pin value for logging into the HSM.
42+
Example: 123456
43+
44+
device.cryptoki.uri A URI of the token/object to be used by tedge-p11-server. See RFC #7512.
45+
Example: pkcs11:token=my-pkcs11-token;object=my-key
46+
47+
device.cryptoki.socket_path A path to the tedge-p11-server socket. Needs to be set when `device.cryptoki.mode` is set to `socket`.
48+
Example: /run/tedge-p11-server/tedge-p11-server.sock
3549
```
3650

3751
```sh command="tedge config list --doc key_uri" title="tedge config list --doc key_uri"
52+
device.key_uri A PKCS#11 URI of the private key. See RFC #7512.
53+
Example: pkcs11:token=my-pkcs11-token;object=my-key
54+
55+
c8y.device.key_uri A PKCS#11 URI of the private key. See RFC #7512.
56+
Example: pkcs11:token=my-pkcs11-token;object=my-key
57+
58+
az.device.key_uri A PKCS#11 URI of the private key. See RFC #7512.
59+
Example: pkcs11:token=my-pkcs11-token;object=my-key
60+
61+
aws.device.key_uri A PKCS#11 URI of the private key. See RFC #7512.
62+
Example: pkcs11:model=PKCS%2315%20emulated
3863
```
3964

4065
## Setup guide

versioned_docs/version-1.5.1/references/tedge-p11-server.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,20 @@ token will be considered for a key.
8585
## Relevant configuration
8686
8787
```sh command="tedge config list --doc device.cryptoki" title="tedge config list --doc device.cryptoki"
88+
device.cryptoki.mode Whether to use a Hardware Security Module for authenticating the MQTT connection with the cloud. "off" to not use the HSM, "module" to use the provided cryptoki dynamic module, "socket" to access the HSM via tedge-p11-server signing service.
89+
Examples: off, module, socket
90+
91+
device.cryptoki.module_path A path to the PKCS#11 module used for interaction with the HSM. Needs to be set when `device.cryptoki.mode` is set to `module`.
92+
Example: /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
93+
94+
device.cryptoki.pin Pin value for logging into the HSM.
95+
Example: 123456
96+
97+
device.cryptoki.uri A URI of the token/object to be used by tedge-p11-server. See RFC #7512.
98+
Example: pkcs11:token=my-pkcs11-token;object=my-key
99+
100+
device.cryptoki.socket_path A path to the tedge-p11-server socket. Needs to be set when `device.cryptoki.mode` is set to `socket`.
101+
Example: /run/tedge-p11-server/tedge-p11-server.sock
88102
```
89103
90104
## Command help

versioned_docs/version-1.5.1/references/tedge-write.md

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,4 +74,46 @@ provided new values will be ignored.
7474
## Command help
7575

7676
```sh command="tedge-write --help" title="tedge-write --help"
77+
tee-like helper for writing to files which `tedge` user does not have write permissions to.
78+
79+
To be used in combination with sudo, passing the file content via standard input.
80+
81+
Usage: tedge-write [OPTIONS] <DESTINATION_PATH>
82+
83+
Arguments:
84+
<DESTINATION_PATH>
85+
A canonical path to a file to which standard input will be written.
86+
87+
If the file does not exist, it will be created with the specified owner/group/permissions. If the file does exist, it will be overwritten, but its owner/group/permissions will remain unchanged.
88+
89+
Options:
90+
--mode <MODE>
91+
Permission mode for the file, in octal form
92+
93+
--user <USER>
94+
User which will become the new owner of the file
95+
96+
--group <GROUP>
97+
Group which will become the new owner of the file
98+
99+
--config-dir <CONFIG_DIR>
100+
[env: TEDGE_CONFIG_DIR, default: /etc/tedge]
101+
102+
--debug
103+
Turn-on the DEBUG log level.
104+
105+
If off only reports ERROR, WARN, and INFO, if on also reports DEBUG
106+
107+
--log-level <LOG_LEVEL>
108+
Configures the logging level.
109+
110+
One of error/warn/info/debug/trace. Logs with verbosity lower or equal to the selected level will be printed, i.e. warn prints ERROR and WARN logs and trace prints logs of all levels.
111+
112+
Overrides `--debug`
113+
114+
-h, --help
115+
Print help (see a summary with '-h')
116+
117+
-V, --version
118+
Print version
77119
```

0 commit comments

Comments
 (0)