Secured Industrial Embedded Linux

AGL Security Blueprint available online on AGL doc website  has been revamped and completed by Vincent Nieutin /
A proposal has been posted online (still on AGL doc website beside the current version: here  ) and is under review by the AGL community.
This proposal includes information of existing Security Blueprint reorganized in a more logical way (bottom to top : hardware to applications,updates) and uses colored sections to highlight and easily identify criticals items.
Some missing parts like SOTA or Secure development have also been added.

[Click here] to download the PDF version of this updated Security Blueprint.

Yocto SDKs or images are currently deployed as monolithic archives.
Projects are more and more complex resulting to larger archives and 
consequently, SDKs or target images updates are not efficient at all.

This talk presents a new solution based on incremental updates and binary
packages deployment, which is closer to standard Linux distribution packaging. 
This solution offers an easy way to update development environment (SDK)
on the development machine and makes packages management simpler on the target side.
This allows among other to install a minimal set of packages in order to reduce the target filesystem size.


AGL leverages Sytemd for several purposes. Example:

  •  setup of applications and services (cgroups, namespaces, autostart, permissions)
  •  use of libsystemd for its programs (event management, dbus interface)
  •  manage users and user sessions

 This presentation explains how using systemd is beneficial for AGL and how the AGL is built to leverage good systemd features.

 It reviews the mechanics of systemd integration and how it is used for user management: PAM integration, privacy management.

 AGL emphasis a clean separation of applications together and with the underlying system layer. It also provides a mechanism to tune how this is done. This talk presents this aspect. see the presentation

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: [here] (AGL/AMM Dresden/Germany Oct-2017)

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 & 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)[here] 

Download older presentations:  [here]

Archived Publications