Skip to content

Commit 7c17a6f

Browse files
authored
Merge pull request #183533 from kgremban/dec22-devicecaperms
Clarify which certificate the filemodes apply to
2 parents f146540 + 28cbdee commit 7c17a6f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-edge/how-to-manage-device-certificates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ If you are using IoT Edge for Linux on Windows, you need to use the SSH key loca
161161
* The certificate files should be owned by the **aziotcs** group.
162162

163163
>[!TIP]
164-
>If your certificate is read-only, meaning you created it and don't want the IoT Edge service to rotate it, set the private key file to mode 0440 and the certificate file to mode 0444. If you created the initial files and then configured the cert service to rotate the certificate in the future, set the private key file to mode 0660 and the certificate file to mode 0664.
164+
>If your device CA certificate is read-only, meaning you created it and don't want the IoT Edge service to rotate it, set the private key file to mode 0440 and the certificate file to mode 0444. If you created the initial files and then configured the cert service to rotate the device CA certificate in the future, set the private key file to mode 0660 and the certificate file to mode 0664.
165165

166166
1. If you've used any other certificates for IoT Edge on the device before, delete the files in the following directory. IoT Edge will recreate them with the new CA certificate you provided.
167167

0 commit comments

Comments
 (0)