In the chapter 2 of our blog series about Security-Enhanced Linux (SELinux), we will discuss the actual implementation of the Policy.
In the chapter 2 of our blog series about Security-Enhanced Linux (SELinux), we will discuss the actual implementation of the Policy.
In this blog series, we delve into the world of Security-Enhanced Linux (SELinux) within embedded systems. As the demand for secure computing environments continues to rise, integrating SELinux into embedded systems has become increasingly pertinent. Through this series, we offer insights, lessons learned, and practical guidance garnered from our first-hand experiences.
Companies who have struggled with finding a stable, secure and highly configurable platform for their interconnected embedded applications will now be able to accelerate their development cycles and enter the market along with Microchip’s PolarFire® System-on-Chip (SoC) Field Programmable Gate Array (FPGA) RISC-V based platform faster thanks to MontaVista Linux CGX.
This is the second episode of a series of Blog Posts on the topic of automotive CAN bus technology.
In the previous posts we talked about reliability and about some kernel bugs our author has worked on. But what do they mean?
In the first episode we talked about the magnitude of the reliability problem for safety critical software. This post focuses on bugs in Linux.
A short look at why we believe the Linux kernel by itself is not suitable for safety critical systems, and why, by extension, Xen is not, either.
Before we dive into the details of CAN Bus, it helps to understand some of the design principles and some of the historical background from when, and why, CAN was invented in the first place, before we show how it fits into the Automotive world of today, and how we can interact with it.
When CentOS 6 was announced to go end of life (EOL) with the 6.10 release, some probably thought “well, all good things must come to an end.” It didn’t take long, but the frantic notices, blogs, and community warnings about upgrading immediately came out and now engineering teams are scrambling to firm up and implement migration plans to CentOS 7 or 8. Or maybe even other Linux platforms. Many probably begrudgingly, as CentOS 6 has served them well, with their products mature and stable. Moving to a newer CentOS platform will cause time consuming migration planning. Engineering execution resources will need to be allocated with possible retesting of a product or solution that was stable, secure, and enjoying high customer satisfaction.
But what if CentOS 6.10 support need not end? This could give product teams breathing room to implement a more controlled and planned migration strategy for their customer base, and more importantly extend life into an already viable solid product.
A PC connected to the internet is vulnerable to attack in a multitude of ways, but the authenticity of the operating system that it runs is not in question.
Are you a home-grown Linux user or do you use a commercial-grade Linux distro provided by a third party such as MontaVista?