With the aim of reducing development costs and cyber risks, two years ago we decided to switch from C/C++ to Rust for the application layers.
 
This presentation provides feedback on the use of Rust for the development of an electric vehicle charging station, carried out in collaboration with an automotive equipment manufacturer. The system is deployed on an embedded Linux platform that implements an application framework optimised for security.
 
We will outline the specifics of using Rust in this context, the advantages it offers, and the challenges we encountered during development and integration, such as interfacing with asynchronous C libraries and the lack of mature, certified Rust cryptographic libraries.
 
We will open the discussion on a review of the Rust community's current efforts to address these challenges.

 
Project's Github page<a href= "https://github.com/tux-evse">ici</a>
Presentation's PDF version <a href="https://iot.bzh/download/public/2025/rust_ev_charger.pdf">here</a>

Rust in embedded systems: feedback on the development of a charging station for electric vehicles

Immerse yourself in the world of charging infrastructure for electric cars with this captivating presentation. Discover the technical architectures behind communications between charging stations and electric vehicles, through the experience of the ‘Tux-Evse’ project.
The talk covers cybersecurity challenges and solutions, lessons learned from using Rust versus C/C++, and the Linux/RTOS cohabitation model for ensuring functional safety.
As a bonus, learn how to build a state-of-the-art smart charging point at home, using open source components.

- [Link to talk](https://www.youtube.com/watch?v=KzgN8LLeh0Q&ab_channel=Codedarmor)
- PDF Link: [IoT-charger-tux-evse.pdf](<https://iot.bzh/download/public/2024/IoT-charger-tux-evse.pdf>)

logo_devfest2024.jpg

Feedback on the use of RUST/Linux in an electric vehicle charging station

devfest.pdf

thumbnail_clement_300x300.png

clement_300x300.png

Tous les programmes ont potentiellement des vulnérabilités qui peuvent être utilisées pour pénétrer dans votre système. Ainsi pour diminuer la portée des cyberattaques, les programmes devraient avoir des accés limités sur le système et ne devrait pas pouvoir écrire, lire, ... d'autres ressources que celles nécessaires.

 

C'est ce que propose les modules de sécurité Linux(LSM) comme SELINUX ou SMACK qui permettent de renforcer le contrôle d'accès obligatoire en créant des règles gérées par un architecte de sécurité.

 

Cette présentation présente comment LSM fonctionne et comment les régles peuvent être automatisées dans un framework comme redpesk.

 

* [Download slides ici](/images/uploads/articles/devfest_8153542108.pdf)
* [devfest website](https://devfest.codedarmor.fr/2021/)

 

<object data="/images/uploads/articles/devfest_8153542108.pdf" type="application/pdf" width="100%" height="600px"/>*

thumbnail_devfest-perros-guirec.png

devfest-perros-guirec.png

Automatisation des modules de sécurité Linux en intégration continue

An introduction to the fundamentals of SMACK and SELinux administration.
 
This conference was presented for the association <a href="https://hack2g2.fr/">HACK2G2</a>.
 
Slides : <a href="https://iot.bzh/download/public/2021/hack2g2/Presentation_MAC.pdf" class="wf_file" title="[click here]">[click here]</a>

small_hack-logo-light-512px.png

thumbnail_hack-logo-light-512px.png

hack-logo-light-512px.png

Introduction to SMACK and SELinux

small_l_portfolio_4.jpg

thumbnail_l_portfolio_4.jpg

l_portfolio_4.jpg

This talk given at the AGL All Member Meeting [VIRTUAL] of Spring 2021 presents how the application framework and its core components can shift from being based on Smack to SELinux.
 
The Linux kernel has many security mechanisms: capabilities, credentials, cgroups, namespaces, security modules, SELinux, AppArmor, Smack, ...
 
The talk reviews their benefits. As of today, the AGL application framework leverages these security features in order to achieve safety, security and privacy of the system, applications and users.
 
The talk summarizes the current state of the application framework.
 
Finally, the talk presents the work done in replacing Smack with SELinux and shows the designs that make the transition transparent to application developers while providing the same level of security.
 
Slides: <a href="https://iot.bzh/download/public/2021/agl-amm/March18_JoseBollo_From-SMACK-to-SELinux.pdf" target="_blank" rel="noopener">[click here]</a>
 
Video: <a href="https://iot.bzh/download/public/2021/agl-amm/March18_JoseBollo_From-SMACK-to-SELinux.m4v" target="_blank" rel="noopener">[click here]</a>

thumbnail_AGL-AMM-logo.png

AGL-AMM-logo.png

From Smack To SELinux

thumbnail_Stephane_300.JPG

Stephane_300.JPG

IoT.bzh investigated on lazy object synchronization techniques combined with an appropriate serialization format and shows that performance can be improved by a ratio from 10 to 100 depending on use cases. This benefits to low-latency and/or high-throughput applications: High frequency sensors, fast CAN messaging, realtime applications, ...
 
Changing serialization format may provide a performance gain from 20% to 50%. To go further, the only solution is to reduce drastically the number of (de)serializations. This can be achieved by adopting a dual internal and external representation for objects coupled with new transport mechanisms between bindings.
 
This talk presents the benchmark results obtained by our team and proposes new ways to boost performance in the AGL Application Framework, including a new binding API v4 compatible with current API v3.
 
Slides: <a href="https://iot.bzh/download/public/2020/agl-amm/IoT.bzh-Boost_AGL_AppFW_performance_by_10-AGL_AMM_July_2020-v1.0.pdf" target="_blank">[click here]</a>
 
Video: <a href="https://vimeo.com/438457064" target="_blank" rel="noopener">[click here]</a>

Boost AGL Application Framework performance by 10+

This slideshow was used as support for a lesson given at "École nationale supérieure de techniques avancées Bretagne (ENSTA Bretagne)" (University of Brittany).
 
It presents many aspect of AGL, its security and its framework. It can be used as starter overview browsing every AGL feature.
 
Download [<a href="https://iot.bzh/download/public/2019/ENSTA/embedded-security-AGL.pdf" target=_blank>here</a>]
&nbsp;

thumbnail_index.png

ensta.png

Embedded Linux, case of AGL. Lesson at ENSTA 2019

thumbnail_Sebastien_300.JPG

Sebastien_300.JPG

This presentation was given at Automotive Linux Summit in Tokyo.
 
AGL natively supports secure micro-services through its Application Framework binder/binding mechanism. A ready to go system may easily run tens or hundreds of micro-services. Consequently monitoring exchanges between binders/bindings is critical. Monitoring may need to be “realtime” to help debugging, or offline when tracking global performances and security issues.
 
This talk starts by presenting current AGL Application Framework monitoring capabilities to track basic inter-bindings communications. It then exposes how existing supervision service can be used to analyze end-to-end transactions when crossing multiple bindings. Finally it illustrates how AGL supervision can leverage Time Serie Database to collect data, allowing monitoring frameworks like Grafana to render a global vision of the system both in term of performance and cybersecurity.
 
Download slides <a href="https://iot.bzh/download/public/2019/ALS_Tokyo_0719/AGL-XDS_Supervision_ALS_Tokyo_2019.pdf" target="_blank">[click here]</a>
&nbsp;

medium_als.png

small_als.png

thumbnail_als.png

als.png

AGL-Supervision : From AGL Supervisor to platform global data collection

thumbnail_Fulup_300.JPG

Fulup_300.JPG

This presentation was given at Automotive Linux Submit in Tokyo.
 
In order to embrace the global automotive ecosystem, AGL micro-services architecture should support not only all Linux in a car, but also seamlessly retrieve data from small ECUs and securely send collected information to the cloud.
 
Because of existing application framework dependencies, as today, AGL bindings run only on Linux. In order to extend to global automotive ecosystem, AGL’s binders/bindings architecture needs to be reviewed. On one hand, remove Linux’s systemD dependencies and extend security model. On a second hand, support ‘alien’ transport protocols including non TCP/IP ones.
 
This talk presents the lesson learned from a POC to run a subset of current AGL binder onto a micro-controller with Zephyr. How to solve binder/binding dependencies, how to map the transport onto a non TCP/IP link, how to extend AGL security model, ...
 
Download slides <a href="https://iot.bzh/download/public/2019/ALS_Tokyo_0719/AGL-uBinder-Fulup-IoTbzh-Tokyo-ALS2019.pdf" target="_blank">[click here]</a>
&nbsp;

AGL-µBinder : a fast, secure and seamless option to connect AGL to small ECUs?

This talk presents, the motivation and options chosen by AGL to address automotive cybersecurity. Its first addresses secure functionally targeted by AGL applications security model, then exposes how we extend the model from Linux entertainment to vehicle to cloud, cluster, telematics, ... This talk remains at the architecture level. It explains targeted security concerns and exposes proposed software architecture but does not aim at digging into specific implementation details.
 
Download pdf slide <a href="https://iot.bzh/download/public/2018/CESA-5.0/Fulup-IoTbzh-CyberSecurity-AGL-CESA-Dec2018.pdf">[here]</a>

thumbnail_sesa.jpeg

sesa.jpeg

Cybersecurity for Connected Vehicle with AGL (Automotive Grade Linux)

small_thierry.jpg

thumbnail_thierry.jpg

thierry.jpg

This talk presents options to bring a subsystem of AGL Application Framework into realtime operating systems like AutoSar Foundation, VxWorks, Zephyr, QNX.In order to bridge smaller controllers with AGL systems, current Application Framework should be skimmed down to a portable, OS-independent and realtime enabled core. To get certified, this small realtime core should be come with 100% code coverage. It should work on microcontrollers, or on a PREEMPT-RT patched linux. It should have a set of realtime API and communication API with the non realtime world. As an example, the presentation shows how to push CAN data to Infotainment.
&nbsp;
 
&nbsp;PDF presentation available <a href="https://iot.bzh/download/public/2018/amm-dresden/realtime_binder_presentation.pdf">here</a>

thumbnail_AGL_logo.png

AGL_logo.png

Skim down AGL Application Framework to bridge AGL with hard realtime subsystems

After a presentation of the security framework that rules the applications, this presentation browse the effective well known use cases of applications. The use cases covered are HTML apps, QML apps, general services, audio 4A service, signal composer service, ... For each use cases are presented the software architecture, the security context, the interaction with the AGL system, the typical dialog between application, binding and services, the programming model using binding version 3 as available in AGL/FF.
 
Download [<a href="https://iot.bzh/download/public/2018/amm-dresden/AGL-app-design.pdf">here</a>]
&nbsp;

AGL application design

small_romain.jpg

thumbnail_romain.jpg

romain.jpg

This presentation will cover the latest test and monitoring tools available in AGL. Most of all, it presents the new test binder answering the following, how to write test for AGL API and how is it integrated within AGL. Then I present the Application Framework Monitoring feature which provides you a binding insights view. At the end, we see another handy Application Framework feature in the name of Supervision that makes available all sort of metrics from the working binder.
 
Download slides [<a href="https://iot.bzh/download/public/2018/amm-dresden/test-monitoring-supervision-romain.pdf" target="_blank" rel="noopener">here</a>]

Moving AGL toward production with the latest test/monitoring tools.

Presentation at Karlsruhe of the ongoing refactoring of binding APIs.
 
The new API named V3 (version 3) is going be compatible with previous versions.
 
Download slides <a href="https://iot.bzh/download/public/2018/f2f-karlsruhe/apiv3-prez-2018-04.pdf" class="wf_file" title="Bindings Api v3">[Click here]</a>

Binding API version 3

The AGL controller is a new binding that was initially developed to address the lack of AGL mechanism to support policy/access-control in AAAA. The outcome of this effort is a fully generic controller that allows to “glue” many different components directly from a simple JSON configuration file. The resulting service is exposed as a native AGL binder. It is a real Swiss Knife and can be used to many different things for applications or services.AGL Controller is a pure Vanila AGL binding. It can be added transparently to any existing binder through the standard application framework import mechanism. The controller is fully compliant with AGL security model and offers for dynamic APIs the same level of protection that AGL already offers to static APIs.AGL controller is powerful and flexible. It allows developers to simply assemble pre-existing AGL APIs, to expose as AGL native binder a legacy/proprietary technologies. Finally it supports Lua as scripting language to glue everything together. Mixing Native/Script language is supported and a developer may choose to fast track demo in Lua script and later to port all/part in native C/C++ to improve performances.The presentation will show the architecture, the different components and will walk though a set of examples. At the end of the talk attendees should have a clean understanding on how to leverage AGL controller in their own applications.
 
Download the detailed PDF presentation: <a href="https://iot.bzh/download/public/2017/AMM-Dresden/AGL-Controller-Binding.pdf">[here] </a>(AGL/AMM Dresden/Germany Oct-2017)

The AGL Swiss Knife for Quick Application Prototyping

xds_arch.png

<div style="float: left; margin: 8px 32px 16px 8px">
<img src="/images/uploads/articles/small_xds_arch_b9c17db1c1.png"/></div>
This presentation was given at ALS 2017 in Tokyo.
 
To reduce as much as possible the entry cost for developing automotive applications, AGL should be integrated to IDE and Source Debugger. Traditionally, installation of an embedded development environment with cross compilation has been difficult and more tortuous that it should. Any developer and especially non system expert, should easily succeed in setting up the AGL development environment on both target &amp; host independently of their preferred OS (Linux, Windows, Mac).
 
This talk presents a solution that tends to a zeroconf installation of AGL development environment, independently of the chosen target/host.The presented solution allows to locally edit sources with your favorite IDE (i.e. Eclipse, Visual Studio Code, Netbeans...) and either compile locally your application or benefit from a remote server. It also shows how to debug application directly from your preferred editor.
 
Download the latest presentation (PDF format):  <a style="font-size: 12.16px;" href="https://iot.bzh/download/public/2017/XDS/presentation/XDS_Presentation_latest.pdf">[here]</a> 
 
Download older presentations:  <a style="font-size: 12.16px;" href="https://iot.bzh/download/public/2017/XDS/presentation/">[here]</a>

X(cross) Development System - make AGL app development easier

systemd.png

<div style="float: left; margin: 8px 32px 16px 8px">
<img src="/images/uploads/articles/small_systemd_ab8708ad2b.png"/></div>
The framework is presented in its current state of January 2017: its history, its features and its goals: opening securely AGL to as many companies as possible. Then, focus will turn to the expected state of the framework at end of 2017, browsing the remaining tasks and giving an agenda. This includes at least these items, reviewed technically and logistically: integration with systemd (cgroup handling, tiny namespacing, ...), permission policy and enforcement, cryptography and PKI for domain protection.
 
Slideshow of the presentation at AGL AMM Winter 2017 Tokyo : <a href="https://iot.bzh/download/public/2017/AMMQ1Tokyo/AGL-security-framework-review.pdf">[here]</a>

AGL Security Framework Review 

agl-dd.png

<div style="float: left; margin: 8px 32px 16px 8px">
<img src="/images/uploads/articles/small_agl_dd_8f1dadcc5c.png"/></div>
Keeping user experience control is critical for every OEM. To enable an easy way to tailor UI and user experience, AGL in general and homescreen in particular should provide a clear separation in between business logic and graphic rendering. This talk propose a new homescreen architecture. In this new approach the homescreen is a platform service accessible through a set of normalized API. Every OEM/Tier1 should be able to easily reshape user experience by simply connecting a new UI on a platform provided homescreen service. The new architecture should support not only both HTML5 &amp; QT user interface, but should also support multi-screens, multi-users, local &amp; remote screens and obviously should implement security built in by design.
 
Download PDF presentation:  <a href="https://iot.bzh/download/public/2017/AMMQ1Tokyo/HomeScreen-Q1AMM2017-Fulup-IoTbzh.pdf">[here]</a>

Homescreen a New AGL Platform Service

(This presentation was given at FOSDEM 2016, Brussels ; see <a href="https://fosdem.org/2016/schedule/event/securehtml5/">link here</a>) 
 Here in IoT.bzh, we are greatly concerned about applications for AGL ; not so much about writing them (though we do provide some !) than providing a easy-to-use framework for automotive developers. 
Automotive development used to be a very specific field, with very specialized developers writing very low-level native code for a very specific brand of car. Meanwhile, newer concepts such as <a href="https://en.wikipedia.org/wiki/App_store">Application Stores</a> and technologies such as <a href="https://en.wikipedia.org/wiki/HTML5">HTML5</a> took power over the mobile (Smartphones &amp; Tablets) market. 
<a href="https://www.automotivelinux.org/software/agl-specification/">AGL specification 1.0</a> now explicitly mentions a store (see page 10) ! If we want to get there and gather developers from various backgrounds around AGL, we need to provide a cross-platform and easy way to publish applications. 
Download slides [<a href="https://iot.bzh/download/public/2016/publications/HTML5_Applications_for_Automotive_Systems.pdf">here</a>]
 
Hence why the meta-iot-agl Yocto layer for AGL, which provides : 
<ul>
<li className="markdownBulletList"> an application manager which instals, starts, stop and uninstalls applications provided as .wgt packages ;</li>
<li className="markdownBulletList"> a binder daemon which passes HTTP REST calls to platform plugins (AM/FM radio, Media Player...) ;</li>
<li className="markdownBulletList"> security, under the form of <a href="http://schaufler-ca.com/">SMACK</a> labels combined with the application manager's isolation logic ;</li>
<li className="markdownBulletList"> sample applications, plain <a href="https://github.com/iotbzh/afm-widget-examples">HTML5</a> ones as well as hybrid ones.</li>
</ul>
 
What is interesting here, is that the hybrid app successfully uses modern frameworks such as <a href="https://angularjs.org/">AngularJS</a> and Foundation !
 
In the talk, I happened to live-modify the hybrid app into the NetBeans IDE. I hope you find it interesting !

large_FOSDEM_logo.svg.png

medium_FOSDEM_logo.svg.png

small_FOSDEM_logo.svg.png

thumbnail_FOSDEM_logo.svg.png

FOSDEM_logo.svg.png

Writing secure HTML5 applications for automotive systems

Next generation of car will be connected and connected car will be attacked. They is absolutely no doubt about those two assertions, and AGL should prepare itself to face this reality. This presentation given during Tokyo <a title="AGL Winter-2016 Schedule" href="http://events.linuxfoundation.org/events/agl-member-meeting/program/schedule">AGL/AMM/2016</a> reviews major security challenges that Automotive Grade Linux should address and will expose some existing technical options to address them.
 
<ul>
<li className="markdownBulletList"> Application Framework</li>
<li className="markdownBulletList"> Security Model</li>
<li className="markdownBulletList"> Applications and Operating System Update</li>
<li className="markdownBulletList"> Secure Boot </li>
</ul>
 
Download slides [<a title="AGL-2.0 Security Architecture Propasal" href="https://iot.bzh/download/public/2016/security/Security-Proposal-AGL20-Fulup.pdf">here</a>]

AGL-2.0 Security Architecture Proposal

Cars are expensive pieces of equipment, yet they represent a huge mass market. Adding Internet connectivity to previous elements generates perfect conditions for the growth of a viable business model on attacking “Connected Cars”. It is already well understood that cars will be connected and connected cars will be attacked. While it's still too early to predict with certainty how “Connected Cars” will be impacted by security flaws, making the assumption that a car should be at least as secure as a TV, a set-top-box or a smart phone should make sense to everyone. This white paper focuses on how Linux best practices security mechanisms that could be used today and within the next couple of years to make connected cars safer and more secure.
 
Download link [<a title=" Automotive Grade Linux Security White Paper" href="https://iot.bzh/download/public/2016/security/Linux-Automotive-Security-v10.pdf">here</a>]

Automotive Grade Linux Security White Paper

This document explains step by step how to setup the development environment for Porter board with AGL distribution and latest Renesas BSP.
 
The following topics are covered:
 
<ul>
<li className="markdownBulletList">instructions to setup the SDK environment based on AGL 1.0 and Renesas BSP</li>
<li className="markdownBulletList">build a cross-platform C/C++ application</li>
<li className="markdownBulletList">deploy the application on a target board</li>
<li className="markdownBulletList">run and debug the application remotely </li>
</ul>
 
Download document [<a href="https://iot.bzh/download/public/2016/sdk/AGL-Application-SDK-Kickstart-on-Renesas-Porter-board.pdf">here</a>].

SDK for Application - Kickstart

This presentation focuses on the features of the AGL SDK solution proposed by IoT.bzh:
 
<ul>
<li className="markdownBulletList">using Docker to create the SDK</li>
<li className="markdownBulletList">SDK demo</li>
<li className="markdownBulletList">future enhancements</li>
</ul>
 
This content has been first presented at the AGL All Member Meeting (Tokyo, Winter 2016)
 
Download slides [<a href="https://iot.bzh/download/public/2016/publications/AGL_SoftwareDevelopmentKit.pdf">here</a>]
 
<h3 className="markdownSubtitle">Part 1: using Docker to create the SDK</h3>
 
<ul>
<li className="markdownBulletList">how to create a binary distribution for application development</li>
<li className="markdownBulletList">how to share this reference environment amongst developers</li>
<li className="markdownBulletList">how to get ubiquity: development on the cloud, on-premises, on a single laptop</li>
</ul>
 
<h3 className="markdownSubtitle">Part 2: SDK demo</h3>
 
<ul>
<li className="markdownBulletList">define a target device</li>
<li className="markdownBulletList">create an application</li>
<li className="markdownBulletList">build and deploy application</li>
<li className="markdownBulletList">run application</li>
<li className="markdownBulletList">debug application remotely</li>
</ul>
 
<h3 className="markdownSubtitle">Part 3: future enhancements</h3>
 
<ul>
<li className="markdownBulletList">AGL plugin for Eclipse</li>
<li className="markdownBulletList">applications profiling</li>
<li className="markdownBulletList">target device emulator through qemu</li>
</ul>

AGL Software Development Kit

With the aim of reducing development costs and cyber risks, two years ago we decided to switch from C/C++ to Rust for the application layers.
 
This presentation provides feedback on the use of Rust for the development of an electric vehicle charging station, carried out in collaboration with an automotive equipment manufacturer. The system is deployed on an embedded Linux platform that implements an application framework optimised for security.
 
We will outline the specifics of using Rust in this context, the advantages it offers, and the challenges we encountered during development and integration, such as interfacing with asynchronous C libraries and the lack of mature, certified Rust cryptographic libraries.
 
We will open the discussion on a review of the Rust community's current efforts to address these challenges.

 
Project's Github page<a href= "https://github.com/tux-evse">ici</a>
Prenetation's PDF version <a href="https://iot.bzh/download/public/2025/rust_ev_charger.pdf">ici</a>

Application framework Publications