text
stringlengths
0
1.82k
• TLS and ACME integration in Caddy
• New plugin-based design allowing for various server types (e.g. DNS, HTTP)
• Let's Encrypt functionality and ease of certificate management
• Go language capabilities showcased through Caddy's simplicity and effectiveness
• Abstraction layer: Caddy as a site-level configuration tool vs traditional web servers like Apache/Nginx
• The benefits of using Caddy as a web server, including its security features and ease of use.
• Plugins available for Caddy, such as the Git plugin and Markdown support.
• Let's Encrypt and its role in providing free TLS certificates.
• Security concerns related to TLS, including PKI issues.
• The importance of transport layer security (TLS) for network applications.
• Importance of using TLS and guaranteeing integrity, confidentiality, nonrepudiation, and authentication
• Risks associated with choosing a trustworthy Certificate Authority (CA)
• Types of issues that can occur when dealing with untrustworthy CAs, such as man-in-the-middle attacks or certificate key theft
• Comparison of different CA entities, including Let's Encrypt and Symantec
• ACME protocol: its role in automating the process of obtaining certificates, benefits of using it, and how it can be implemented by any CA
• Discussion on Let's Encrypt and ACME protocol
• Validation process for certificates and its security
• Impact of free certificates on the CA industry
• Role of automated certificates in making CAs more accountable
• Importance of extended validation certificates for added trust and business value
• Update from web browsers regarding DV validated certificates vs EV
• TLS SNI challenge and HTTP challenge limitations
• ACME protocol challenges: HTTP challenge, TLS SNI challenge, and DNS challenge
• DNS challenge advantages (no port required) and disadvantages (manual setup or API access)
• Caddy's support for DNS providers and the ability to automate certificate renewal
• Go libraries for TLS management, including rsc/letsencrypt and dkumor/acmewrapper
• Upcoming conference events: GopherCon Brazil (November 4-6), dotGo (October)
• Discussion of KubeCon and potential talks
• Release of Hewlett-Packard's `gas` library for static code analysis
• Challenges with false positives in static analysis tools
• New Go packages: `sync.errgroup`, `SafeSQL`, and `func.test`
• Go wrapper for .NET, allowing communication between the two ecosystems
• Discussion of creating a cross-platform GUI library
• Carlisia Thompson's transition from Atom to Vim for coding
• Fatih's tutorial notes and Jessie Frazelle's dot-vimrc file in helping Carlisia learn Vim
• Release process and changelog for the Vim-go package
• Exercism as an open-source project for learning and contributing to Go development
• QUIC implementation in Go by Lucas Clemente, allowing for faster HTTP communication with benefits like seamless network changes
• Discussion of Mosh (mobile shell) project
• Use of UDP for connection reliability
• Shout out to Wireshark and TCP Dump for network protocol analysis
• Custom configurations and filters in Wireshark
• TCP Dump's ability to read pcap files
• Review of protocols discussed on the show
**Erik St. Martin:** We are back for episode number 14. On the show today we have myself, Erik St. Martin, we also have Brian Ketelsen. Say hello, Brian...
**Brian Ketelsen:** Hello!
**Erik St. Martin:** ... and Carlisia Campos.
**Carlisia Thompson:** Hi!
**Erik St. Martin:** And our special guest today is Matt Holt, who we're gonna talk a bit about TLS, ACME and his own project, Caddy. How are you doing, Matt?
**Matt Holt:** Hi there, good.
**Erik St. Martin:** So we're having a little bit of déjà vu here because we did have you on the show when we were kind of kicking things off and doing some dry runs and all that jazz, so this is actually fun because you've had some new things come out for Caddy recently.
**Matt Holt:** Yeah.
**Erik St. Martin:** And we're a bit more seasoned now, so I think that works well.
**Matt Holt:** Yeah, the timing is good.
**Erik St. Martin:** So wanna kick it off with Caddy? Because I think that's probably the most common thing everybody knows you for. You wanna talk a little bit about what Caddy is and kind of your motivations behind creating it?
**Matt Holt:** Sure. And that will be a good way to segue into the TLS and ACME conversation. Caddy is an HTTP2, HTTPS default web server. It's written in Go, of course. About two weeks, we released Caddy 0.9, which was a pretty big release because I rewrote it from scratch, as a whole new architecture, inverted all th...
**Erik St. Martin:** This is Meek's Core DNS project, right?
**Matt Holt:** Yeah.
**Erik St. Martin:** It's kind of his rewrite of Sky DNS.
**Matt Holt:** Yep, so that's a Caddy plugin which will be available soon.
**Brian Ketelsen:** Also, this is a plugin to Caddy, rather than core DNS kind of leveraging shared libraries; it's actually the other way around, where Caddy takes plugins. Am I understanding that correctly?
**Matt Holt:** Right. I was really excited when he forked this, thinking that it would be beneficial for a DNS server and it turns out that it is. But the problem is that you have a bunch of duplicated code, you have to maintain a fork, and so to alleviate some of that pressure and to help Caddy serve a wider audience ...
**Erik St. Martin:** \[03:53\] Wow, that's awesome. So I wanna kind of circle back for one second, because you happened to mention that 0.9 was a complete rewrite, so how long did that take and what was the motivation behind kind of just scrapping and starting over? Was it new functionality and new ways of looking at y...
**Matt Holt:** Yeah, so people's feedback really expanded my vision a lot of what they wanted and what was possible and what Caddy really was. On day one for me, Caddy was just a web server that makes it easy to spin up a new website in just a matter of seconds, but after the launch of Let's Encrypt and more people usi...
**Brian Ketelsen:** Wow.
**Matt Holt:** But I love Go, and it was a pleasure.
**Erik St. Martin:** And this is all while maintaining and doing bug fixes to prior releases, right?
**Matt Holt:** Yeah, one or two... Admittedly, I started maintaining the older release once I got about two months into the rewrite.
**Erik St. Martin:** PR's accepted. \[laughs\]
**Brian Ketelsen:** That's right.
**Matt Holt:** Yeah.
**Brian Ketelsen:** So we get awfully excited about Caddy around here, mostly because -- well, actually, there's two reasons. One, everything that I serve on the web is served through Caddy and it has been for, I guess, about a year-and-a -half now, almost since Caddy was released. So we love Caddy a lot.