Verified boot and free software: reconciling freedom and security
Action | Key |
---|---|
Play / Pause | K or space |
Mute / Unmute | M |
Toggle fullscreen mode | F |
Select next subtitles | C |
Select next audio track | A |
Show slide in full page or toggle automatic source change | V |
Seek 5s backward | left arrow |
Seek 5s forward | right arrow |
Seek 10s backward | shift + left arrow or J |
Seek 10s forward | shift + right arrow or L |
Seek 60s backward | control + left arrow |
Seek 60s forward | control + right arrow |
Decrease volume | shift + down arrow |
Increase volume | shift + up arrow |
Decrease playback rate | shift + comma |
Increase playback rate | shift + dot or shift + semicolon |
Seek to end | end |
Seek to beginning | beginning |
Share this media
Download links
HLS video stream
You can use an external player to play this stream (like VLC).
HLS video streamWhen subscribed to notifications, an email will be sent to you for all added annotations.
Your user account has no email address.
Information on this media
A growing number of modern computers, whether they’re traditional x86 desktops and laptops or embedded devices ship with some form of verified boot mechanism. In practice, it often means that only bootup software allowed by the manufacturer can run on those computers, causing great harm to freedom, but also to security. Using asymmetrical cryptographic algorithms for signing these binaries with a private key kept secret by the manufacturer and a public key often stored in read-only memory, it becomes impossible for end users to build, install and run free bootup software on their devices.
However, there are a few examples of devices on which verified boot is implemented in a way that allows end users to stay in control of their devices. Namely, Chrome/Chromium OS (CrOS) devices such as Chromebooks implement reliable verified boot in a way that doesn’t conflict with software freedom, on purpose. Taking things up a notch, verified boot is implemented with free software, both at the bootup software and embedded controller firmware levels.
Paul Kocialkowski
Paul Kocialkowski started using free software in 2008 and soon gained interest in software freedom, with a particular emphasis on running fully free software. After breaking his Openmoko FreeRunner, he took at shot at Replicant, the fully free version of Android. He soon became involved in active development and has been the lead developer of the project since 2012.
Driven by a growing interest in embedded devices, he took charge of the single board computers and plug computers freedom comparisons on the Free Software Foundation’s website. Recently, he’s been working on freeing mobile and embedded devices at the lower levels, contributing to the U-Boot, Flashrom, Coreboot, Libreboot and Linux projects.
Other media in the channel "Sécurité"
- 82 viewsMOWR, A virustotal-like service for web malwaresAugust 7th, 2016
- 273 viewsMIG: Investigate 1,000 endpoints in 10sAugust 8th, 2016
- 59 viewsComplex malware & forensics investigationAugust 7th, 2016
- 129 viewsUsing and abusing MISP to track campaignsAugust 7th, 2016
- 18 viewsBuilding A Poor man’s Fir3Ey3 Mail ScannerAugust 8th, 2016
- 16 viewsHands-on security for DIY projectsAugust 7th, 2016