From 4f8ed2d4348d9b2c08de43fb46490f9e304a5c88 Mon Sep 17 00:00:00 2001 From: Tatiana Leon Date: Tue, 8 Jul 2025 10:24:38 +0200 Subject: [PATCH] cccs: ccimx6ul: drop exception for `data` partition and client certificates Until DEY 5.0, the ccimx6ul platform was the only one that did not include a `data` partition. As a result, `cccsd` had to store the client certificate from Remote Manager in the root filesystem, under `/etc/ssl/certs` by default. This setup caused issues after a software update, as the received client certificate would be lost, making the device unable to reconnect to the server until the certificate was manually reset from Remote Manager. The same problem occurred in dual-boot systems, since the certificate was stored in the rootfs of the current bank and was not accessible from the other bank. To avoid this situation, the ccimx6ul used the `remotemanager.digi.com` endpoint instead of `edp12.devicecloud.com`, as the former does not support or deliver client certificates. Now that DEY 5.0 includes a `data` partition in the ccimx6ul partition table, we can remove this exception and allow the use of `edp12.devicecloud.com`, storing the certificates persistently in the `data` partition. Signed-off-by: Tatiana Leon --- meta-digi-dey/recipes-digi/cccs/cccs_git.bb | 7 ------- 1 file changed, 7 deletions(-) diff --git a/meta-digi-dey/recipes-digi/cccs/cccs_git.bb b/meta-digi-dey/recipes-digi/cccs/cccs_git.bb index dc62ab2a0..7e623890c 100644 --- a/meta-digi-dey/recipes-digi/cccs/cccs_git.bb +++ b/meta-digi-dey/recipes-digi/cccs/cccs_git.bb @@ -87,13 +87,6 @@ do_install() { fi } -do_install:append:ccimx6ul() { - if [ -z "${CCCS_CONF_PATH}" ]; then - sed -i "/url = \"edp12.devicecloud.com\"/c\url = \"remotemanager.digi.com\"" ${D}${sysconfdir}/cccs.conf - sed -i "/client_cert_path = \"\/mnt\/data\/drm_cert.pem\"/c\client_cert_path = \"\/etc\/ssl\/certs\/drm_cert.pem\"" ${D}${sysconfdir}/cccs.conf - fi -} - pkg_postinst_ontarget:${PN}-daemon() { # If dualboot is enabled, change the CCCSD download path and set on the fly to yes on the first boot if [ "$(fw_printenv -n dualboot 2>/dev/null)" = "yes" ]; then