Still no CI for this. You can send that separately on top, the series looks fine otherwise. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

Hi, This question stems from the thread titled "The security of NTP". If we do go with NTS, it looks like we're going to need an Internet connection to the embedded platform. Is that acceptable? The

Cool. I'll check out NTS and I'll just respond in this group with silly questions as I stumble along (I'm new to CIP and am not a security expert at all). -- Mohammed Billoo MAB Labs,

Hi Mohammed

Daniel, Thanks for pointing that out. Since CIP is reliant on available packages on particular versions of Debian, would the process/workflow then be to wait for tlsdate to be available in Buster and

Test - please ignore. Thanks, Neal Caidin Linux Foundation (sent from a personal account)

From: Venkata Pyla <venkata.pyla@...> Signed-off-by: Venkata Pyla <venkata.pyla@...> --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md

From: Venkata Pyla <venkata.pyla@...> Use 'TARGET_IMAGE' to pick respective image file when starting qemu by default 'TARGET_IMAGE' uses "cip-core-image". to pick different target image

From: Kazuhiro Hayashi <kazuhiro3.hayashi@...> Identified security packages are added to the target image and that will be used for IEC-62443-4-2 evaluation Signed-off-by: Kazuhiro Hayashi

From: Venkata Pyla <venkata.pyla@...> Patch series for Security changes for IEC-62443-4-2 evaluation Kazuhiro Hayashi (1): cip-security: Add packages for IEC-62443-4-2

Daniel, Pavel: Thanks for the feedback. Is tlsdate a better alternative (https://github.com/ioerror/tlsdate/)? The only caveat if using tlsdate (or any sort of time mechanism that relies on a

FYI Kind regards, Chris

Hello, During the last CIP Core meeting we discussed about license compliance for CIP core image releases. In particular, we talked about how to make sure that users can get exactly the same source

Hi Jan, Patches give you greater visibility (all cip-dev members), but I can see some benefits in using MRs as well: * merge when the pipeline succeeds * map issues with the patches that close them *

Hi Pavel, *I renamed the subject and added cip-security to Cc

Hi, CIP kernel team has released Linux kernel v4.19.134-cip31. The linux-4.19.y-cip tree has been updated base version from v4.19.132 to v4.19.134, In addition, the rcar-du and display features have

Hi! v4.4.231-cip47-rt30 should be available at kernel.org. Trees are available

The conflict was due to a missing rename back in 4.4: e4a81bfcaae1 ("x86/fpu: Rename fpu::fpstate_active to fpu::initialized"). I've fixed up the patch and queued it for 4.4, thanks for pointing

You are asking about something we did back in 2018. I can't remember what I did last week :) If you provide a backport that works, I'll be glad to take it. The current patch does not apply cleanly