HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pion
dtls
Go2020–2026
pion / dtls

dtls

DTLS 1.2 / 1.3 implementation for Go

Security & PrivacyNetworking
Explore on GitHubRead Hacker News discussions
3Distinct people
7Mentions
0Explicit recommenders
714GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

DTLS 1.2 / 1.3 implementation for Go

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2020-04-21 08:22:53 UTC to 2026-10-16 20:59:02 UTC.

01232020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC312
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

7 sources
JoTurk·Oct 16, 2026Submission

Tell HN: Anthropic found 36 bugs (6 CVEs) in Pion, OpenAI missed them

We added Pion DTLS to Anthropic's OSS scanner last week (https://github.com/anthropics/oss-scanner/pull/93), and today we woke up to a report with 36 bugs, including 6 security vulnerabilities: 2 critical, 3 high, and 1 moderate. Four of them affect WebRTC. Some of these vulnerabilities have been sitting in the codebase for over 4 years, surviving years of testing and security scans. It's funny that our inboxes are constantly spammed with AI-generated security reports from people using Codex and Claude, most of which flag pointless issues. Yet somehow, none of them caught these. The funniest part? Anthropic also found 3 bugs that OpenAI's internal code review missed. I had asked OpenAI to review a new DTLS API since they use Pion and had a use case for it in SPED. Their review didn't flag any bugs. Anthropic found an authentication issue,
Read the rest
a deadlock, and a TLS KeyUpdate bug (Maybe their model ignored this one because it's not a WebRTC issue). Luckily, the API hasn't been released yet. The fixes: https://github.com/pion/dtls/pull/1236 Here are the security advisories for the CVEs Anthropic found (all of them are pre-chatgpt!): Critical: DTLS handshake signature confusion allows peer impersonation - https://github.com/pion/dtls/security/advisories/GHSA-7c2r-jhm9-43vf Critical: Client authentication bypass through premature session caching - https://github.com/pion/dtls/security/advisories/GHSA-hhpj-h56m-9f2p High: Client authentication bypass with shared session stores - https://github.com/pion/dtls/security/advisories/GHSA-cqhp-ggp7-58qj High: Unbounded handshake cache allows remote memory exhaustion - https://github.com/pion/dtls/security/advisories/GHSA-jm57-r6vj-mwg9 High: Oversized RSA keys allow CPU exhaustion - https://github.com/pion/dtls/security/advisories/GHSA-jp25-wc3w-p9xp Moderate: Repeated certificate verification allows CPU exhaustion - https://github.com/pion/dtls/security/advisories/GHSA-qpgj-64qg-5m4r The most annoying part is that neither company's models were willing to help with verifying or filtering the bugs, so we had to manually review them one by one (Spent all day :/
8 points · Open discussion
Sean-Der·Jul 30, 2022
This has been really fascinating to watch. A patch just landed in Pion DTLS[0] yesterday to make the fingerprinting harder. I don't remember all the commits, but the Tor devs are absolutely amazing to work with and submit patches that are pretty much perfect :) If you haven't had a chance to investigate WebRTC I really think it is worth it. WebRTC gives up P2P Data/Media everywhere and it is really hard to block (because so many companies depend on it). To me it really feels like the best path forward to circumventing control. It also is a great career move. You can help people build conferencing tools during the day, and Censorship Circumvention at night. [0] https://github.com/pion/dtls/commit/de299f573c3e44fece16f09c...
In Tor is fighting and beating Russian censorship
Sean-Der·Mar 21, 2022
I have had offers to be paid to work on specific things for github.com/pion/webrtc and github.com/pion/dtls. I took one and it wasn't as great as I thought it would be. I really value the autonomy/independence I have now. I enjoy not having to make compromises. No deadlines to meet, no business goals and no creating stories for promotion. Instead I make the software as good as I can. Working a job unrelated to your Open Source project is the best place to be. You will probably make more money. You don't have to worry about clients paying on time. You don't have to worry about things like health insurance or 401k. Open Source is also great for the resume. Since it is all public you have a body of work that makes it much easier to get another job.
In How to Pay Professional Maintainers
Sean-Der·May 16, 2021
I started (but many many others contributed) to the Go implementation of WebRTC Pion WebRTC https://github.com/pion/webrtc if you aren't familiar with WebRTC it is really amazing tech. Check out some of the projects on https://github.com/pion/awesome-pion. Stuff like https://github.com/giongto35/cloud-game continues to blow my mind :) Along the way I worked on a Go implemenation of DTLS that gets used on its own a bit https://github.com/pion/dtls In another life I wrote Therac https://github.com/sean-der/therac. A PHP debugger that was viewable from a browser. I was a remote at the time (2015) and it was a great tool to use with others. I also wrote fail2web https://github.com/sean-der/fail2web a web frontend to fail2ban
In Ask HN: What are some tools / libraries you built yourself?
Sean-Der·Nov 10, 2020
I am super happy that I invested in Go. I ended up working on TURN, WebRTC and DTLS and feel I made the right choice. The impact vs time spent was worth it. I don't think there is any other language I would have had a better experience. Either it is too niche, or it is so popular that the community is anemic. * https://github.com/pion/dtls * https://github.com/pion/webrtc * https://github.com/pion/turn Go is really great as a 'teaching language'. I have seen lots of software pop up that was inspired by reading the Pion code. I think that is great, it is much harder to read and learn from other languages. Also really great for contributions. I get so many people making their first Open Source commit. The languages simplicitly really makes it easy. The most frustrating thing about Go isn't even the language, it is the community for me. It i
Read the rest
s very business/corporate focused. Everything is all about Kubernetes/cloud. I apply for conferences/meetups non-stop, but never have any luck. It is always the same company reps. I am envious of the Rust community here, but maybe grass is always greener on the other side?
In Eleven Years of Go
Sean-Der·May 29, 2020
This is a cool utility that someone contributed to Pion! I get lots of questions around why certain calls need TURN, or how P2P works in general. When you run it you will get output like sean@siobud:~/stun$ ./stun-nat-behaviour 2020/05/29 23:18:31 Connecting to STUN server: stun.voip.blackberry.com:3478 2020/05/29 23:18:32 Local address: 0.0.0.0:56304 2020/05/29 23:18:32 Received xormapped address: 165.227.221.230:56304 2020/05/29 23:18:32 Received xormapped address: 165.227.221.230:56304 2020/05/29 23:18:32 NAT mapping behavior: endpoint-independent 2020/05/29 23:18:32 Local address: 0.0.0.0:41265 2020/05/29 23:18:32 Received xormapped address: 165.227.221.230:41265 2020/05/29 23:18:32 NAT filtering behavior: endpoint-independent If you aren't familiar with Pion it is a collection of libraries to solve WebRTC/VoIP/Io
Read the rest
T problems. It is by a diverse set of contributors, and we are always looking for me! I personally want to get this space to be more like the web, owned by individuals instead of companies. Check out our other popular libraries * https://github.com/pion/webrtc * https://github.com/pion/ion * https://github.com/pion/dtls
In Show HN: pion/stun-nat-behaviour. Do you know your NAT rules?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.