Manuel Bachmann

Everyone understands why a car should be more secure than a phone. Embedded applications typically request special privileges such as playing sound, sending SMS or geolocating. Those running on vehicles, while having the same requirements, need to be more strictly constrained to prevent dramatic consequences on equipment, driver and passengers.

The most common motivation to ignore security is cost reduction and time-to-market. Developing secure HTML5 applications should be smooth and simple. This talk presents a model of architecture leveraging modern tools such as Gulp, Angular and Foundation6 to simplify the production of applications for the automotive industry, while respecting strong security constraints.

This talk focuses on the GNU/Linux AGL distribution and responds to the following concerns : - How to guarantee that malicious HTML5 applications cannot impair security ("Never trust HTML5 code") ? - How to enforce privilege isolation through SMACK ? - How to enforce code isolation via dynamic plugin loading/unloading ? - How to debug code on both the target and development station ? - How to support mixed HTML5/native applications without impairing security ?

We will also take a look at the AGL HTML5 stack, its development and integration pace in AGL distribution.

Many state-of-the-art graphical applications and frameworks still use direct X11 and legacy GL API calls. As we need to move further and follow new evolutions of the UNIX display stack, especially on embedded platforms, we need to adapt or wrap our codebase to Wayland and GLES.

X has been part of UNIX ecosystem for more than 20 years now ; it will now progressively become “deprecated” in favor of Wayland, which targets both desktop and mobile platforms. On the other hand, while OpenGL has been extensively used will still be, its numerous API evolutions, breakages and target profiles tend to render old code unusable on new implementations, and especially those of current Wayland compositors.

Starting from a practical development case (an application -OpenCPN- using deprecated OpenGL1 calls and a toolkit -wxWidgets- which itself has not been fully ported to Wayland yet), we will describe how we managed to get it accelerated-running on Weston by wrapping :

• X11/GLX and wxWidgets-GDKX calls with our EGLX library ;

• OpenGL 1 calls with the jwzGLES library.

We will finally explain what efforts remained pending to obtain a fully-working port of the application (deprecated concepts in core code, API misuse…) to an embedded GNU/Linux platform.