Insufficient.Coffee

My friend Christophe Brocas has just published a retrospective on the ten years since we unveiled the ACME protocol to the world.

After taking a year off from organizing OSCW 2025, I'm back for next year's event in Taipei.

I'll be attending the Real World Crypto Symposium in Toronto in two weeks time, and after that, I'm once again co-organizing the Open Source Cryptography Workshop.

As I mentioned in my post about attending Real World Crypto 2023 and the Open Source Cryptography Workshop, I've given a talk discussing Rustls-FFI and the work to allow curl and libcurl to use the Rust-based, memory-safe Rustls TLS library in a talk call…

At this point I'm supposed to be in Tokyo, attending the Real World Crypto Symposium in Tokyo next week, and after that, I'm co-organizing and speaking at the Open Source Cryptography Workshop.

I'll be attending the Real World Crypto Symposium in Tokyo next week, and after that, I'm co-organizing and speaking at the Open Source Cryptography Workshop.

I'd never thought about the logistics of moving donated blood around.

Firefox is the only major browser that still evaluates every website it connects to whether the certificate used has been reported as revoked.

Since Firefox Nightly is now using CRLite to determine if enrolled websites' certificates are revoked, it's useful to dig into the data to answer why a given certificate issuer gets enrolled or not

Firefox Nightly is now using CRLite to determine if websites' certificates are revoked — e.g., if the Certificate Authority published that web browsers shouldn't trust that website certificate.

Due to a variety of factors, Mozilla changed venues for our 2017 winter all-hands meeting to Austin, Texas, and Austin being a city with relatively poor commercial airline connectivity, ticket prices were fairly high even for me to fly there from Phoenix

I have had business dealings requiring me to visit Berlin regularly for the last 5 years, and in 2018 I finally made the trip outside of the city to Strausberg Airport to rent a Cessna 172SP Skyhawk

While I lived in a lot of different places as a child, I came of age along the Florida panhandle, and for that reason it'll always hold a special place in my heart

I've had a lot more opportunity to travel since I joined Mozilla, and it eventually occurred to me: I could rent aircraft in some of these places I was visiting, and see those places in a different way

I've been running this blog on an LTS version of Ubuntu that has recently halted Long Term Support, so while migrating data I'm also reworking parts of this blog, including a long-anticipated move from tacticalsecret.com (what a ... term) to the timeless…

CRLite pushes bulk certificate revocation information to Firefox users, reducing the need to actively query such information one by one.

CRLite is a technology to efficiently compress revocation information for the whole Web PKI into a format easily delivered to Web users.

CRLite is a technology proposed by a group of researchers at the IEEE Symposium on Security and Privacy 2017 that compresses revocation information so effectively that 300 megabytes of revocation data can become 1 megabyte.

Firefox for Android (Fennec) now supports the Web Authentication API as of version 68.

I gave a lightning talk at our Mozilla All-Hands meeting about CRLite, a new technology for delivering revocations for the Web PKI to all clients in a very compressed form.

Web Authentication is now enabled in Firefox Nightly, with intent to ship in version 60.

At Mozilla's Austin All-Hands I gave a lightning talk about Web Authentication, which is our best technical solution to the scourge of phishing today.

Certificate Revocation Lists (CRLs) are a way for Certificate Authorities to announce to their relying parties (e.g., users validating the certificates) that a Certificate they issued should no longer be trusted.

We're changing the methodology used to calculate the Let's Encrypt Statistics page, primarily to better cope with the growth of Let's Encrypt.

I've been supplying the statistics for Let's Encrypt since they've launched.

Our deprecation plan for the SHA-1 algorithm in the public Web, first announced in 2015, is drawing to a close.

The Phoenix DevOps Meetup has asked me to do a walk-through of how to encrypt a website using Let's Encrypt for their February meetup.

The electoral college has legitimized an agenda that seeks to tell many of my friends and colleagues that they are not welcome in America.

Yesterday Let's Encrypt reached a new milestone: the unique set of all fully-qualified domain names in the currently-unexpired certificates issued by Let's Encrypt is now 10,022,446

I'm training to be able to fly in clouds and other poor visibility situations.

I am training right now for my instrument rating add-on to my private pilot certificate.

Today at the RMLL conference's security track I'm talking about some of the challenges, decisions, and trade-offs that occurred while launching Let's Encrypt, in a talk I've called Let’s Encrypt: The Road To Encrypting All The Things.

This is a quick status update from the Early Impacts of Let's Encrypt post

During the months I worked in Let's Encrypt's operations team I got fairly used to being the go-to man for any question that a database query could solve

Gathering data from Certificate Transparency logs, here's a snapshot in time of Let's Encrypt's certificate issuance rate per minute from 15-21 January 2016

I spent some time over the last week working up a safe Content Security Policy for this website

All the first Let's Encrypt certs for my websites from the LE private beta began expiring last week, so it was time to work through the renewal tooling

A bigger blog post will have to wait, but just as a brief note: Let's Encrypt is now publicly trusted.

One of the advantages to being part of the Let's Encrypt team is early access to the closed beta.

GatorLUG has invited me to talk about Let's Encrypt at their April 2015 meeting.

I've posted a new version of my Bootstrap Icons theme for JsonResume

Last night I received this political cartoon in my email:…

Because many of the devices in the IoT are headless and have limited ability to interact with their owners, there needs to be a way to authenticate them without passwords, and without the shortcomings of the existing 0000 and 1234 problems in the Bluetooth

There's a quirky little project on the Internet proving once again that semi-structured data is just plain fun: JSONResume.org.

Where the Internet of Things meets locations in the physical world, I envision scores of devices networking together to make life more efficient…

Using an Electric Imp and two Vegetronix VH400 soil moisture sensors, I am now able to monitor the water content of two locations in my garden.

The public authentication problem is one we have all learned to solve with intuition: How do I decide to trust a new person?

The Internet of Things is imagined to be a interconnection of sensors and physical devices of all kinds into the world’s information systems: a collection of machine-to-machine communication devices used to gather and distribute information about the worl…