Author(s):	Aleksa Sarai
Location	Room 5
Date	jan Wed 15	Days Raw Files
Start	14:25	First Raw Start	error-in-template
Duration	0:45:0	Offset	None
End	15:10	Last Raw End
Chapters
Total cuts_time	None min.

https://lca2020.linux.org.au/schedule/presentation/62/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Securing_Container_Runtimes_How_Hard_Can_It_Be.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	In the past few years, we have seen a varied array of different security vulnerabilities in container runtimes (often resulting in breakouts or other severe attacks against the host system). As a result, some members of the community have been looking into whether there are more fundamental issues at play which could help resolve some of these problems. In this talk, we will discuss what are possible problem areas for container runtime security and our attempts to solve some of these issues through both kernel-space and user-space protections -- and how some of these protections may help many other programs outside the container runtime community secure themselves against attackers. markdown
Comment:	production notes