veyepar: (Re)solving an appliance traffic dilemma with the DNS loophole

Author(s):	Marco Slaviero
Location	Cedarwood
Date	oct Fri 12	Days Raw Files
Start	10:00	First Raw Start	09:28
Duration	00:45:00	Offset	0:31:24
End	10:45	Last Raw End	10:46
Chapters
Total cuts_time	None min.

https://za.pycon.org/talks/50-resolving-an-appliance-traffic-dilemma-with-the-dns-loophole/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

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

State:
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:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Cloud-based components are an all too common speed bump when installing new gear or software. While not an issue in home networks, outbound connections are shunned by default in regulated environments. Enabling communications between the newly installed technology and its cloud service then involves change control requests, committees, firewall admins, and (worst of all) delays... hardly the high-speed future we were promised. Product builders: it doesn't have to be this way. Right now in your network one type of traffic almost certainly can exit your network without restriction: DNS. That VOIP network you think is isolated? Pretty good chance it can resolve DNS. This is the story of how we grew one of the larger DNS overlay networks around using Python Twisted. We built a secure and reliable channel between thousands of appliances (hardware and virtual) and hundreds of servers, over the inherently unreliable DNS. The talk covers designing and building custom network channels in Twisted, Twisted limitations we bumped into, unexpected DNS behaviours, challenges in scaling the channel, and more. Network knowledge is useful but not necessary to follow along, and while we used Twisted, the lessons are applicable in other frameworks too. If you've got an hankering for network code, then this heady mix of network stacks and Python hacks is for you! markdown
Comment:	DO NOT UPLOAD production notes