BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.cfgmgmtcamp.org//8CZXZK
BEGIN:VTIMEZONE
TZID:Europe/Brussels
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-2024-8CZXZK@cfp.cfgmgmtcamp.org
DTSTART;TZID=Europe/Brussels:20240206T125000
DTEND;TZID=Europe/Brussels:20240206T125500
DESCRIPTION:Since the beginning of the project\, salt has used a custom cry
 ptographic implementation based on RSA to encrypt messages between masters
  and minions over what is called the transport.  I will present a new sche
 me that uses a standard implementation of mTLS.  Although salt is supremel
 y modular\, the crypto backend was never made pluggable.  The builtin cryp
 to implementation is spread across several source files and is closely int
 erconnected with both the ZeroMQ and TCP transports.  Rather than insert a
  new crypto backend alongside the existing crypto implementation at each p
 oint across the several files\, the new crypto backend uses a new\, simple
 r design\, mainly because mTLS can be used out of the box in contrast to c
 ustom RSA key management\, trust on first use\, static auth token seed (fo
 r reals)\, etc.  Because of the close mixing of transport and crypto code\
 , the opportunity was taken to introduce WebSockets as a new transport as 
 well.  Great\, so what about post quantum crypto?  Since the mTLS backend 
 is not implemented in the source code\, crypto algorithms and primitives\,
  including those certified for PQC\, FIPS\, etc. can now be easily swapped
  in with no change to the user code.
DTSTAMP:20261013T170955Z
LOCATION:D.Aud
SUMMARY:Implementing Post Quantum Crypto for SaltStack - Justin Findlay
URL:https://cfp.cfgmgmtcamp.org/2024/talk/8CZXZK/
END:VEVENT
END:VCALENDAR