BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.all-systems-go.io//all-systems-go-2026//HHJRVC
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-all-systems-go-2026-TL3KGN@cfp.all-systems-go.io
DTSTART;TZID=CET:20260930T171500
DTEND;TZID=CET:20260930T172000
DESCRIPTION:When you lock your systemd-homed enabled Linux desktop today\, 
 your home directory (including the desktop session) is fully frozen. This 
 happens because systemd-homed uses a single cryptographic key (the LUKS vo
 lume key) and throws it away during lock. Want to lock away just your cred
 entials as on a normal screen lock while keeping music playing and notific
 ations coming through? You can't.\n\nThis talk presents the work done as p
 art of the systemd STF grant to extend the systemd-homed's key hierarchy t
 hat fixes this issue.
DTSTAMP:20260710T215743Z
LOCATION:Loft
SUMMARY:Rethinking systemd-homed's Key Hierarchy - Dhanuka Warusadura
URL:https://cfp.all-systems-go.io/all-systems-go-2026/talk/TL3KGN/
END:VEVENT
END:VCALENDAR
