HNHacker News
TopNewBestAskShowJobs

mcpherrinm

4,544 karma · joined January 24, 2010

submissionscomments
mcpherrinm··on Parallel Reconstruction of Lawful TLS Wiretapping
CAA checking is mandatory, so you can always restrict to a given CA.

To get complete control with DNSSEC, you also need the accounturi and validationmethod extensions (which you need to guarantee only your account can issue, and only with the DNS validation type).

Those aren't yet mandatory, but you can restrict to a CA today which implements them, like Let's Encrypt.

mcpherrinm··on Stop Advertising in Your Commits
The post seems to be down so I am not quite sure what it says, but Co-Authored-By trailer is what Claude does. I'm not quite clear what you're suggested that's different from what Claude does - just default to off instead of default on?

> Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

mcpherrinm··on Three men are facing charges in Toronto SMS Blaster arrests
It doesn't matter what the network is doing; the phone needs to disable 2g. There's various ways to get the phone to downgrade to 2g otherwise, eg https://montsecure.com/files/2021_downgrade.pdf

Android has it as a toggle: https://source.android.com/docs/security/features/cellular-s...

iPhone disables it for phones in lockdown mode.

mcpherrinm··on Three men are facing charges in Toronto SMS Blaster arrests
There's zero spam filtering interfering this way, and you can target your messages very precisely.
mcpherrinm··on Three men are facing charges in Toronto SMS Blaster arrests
2g networks didn't have the phone verify the network, so yes they can do this.

At least as of today, most phones have an option to turn off 2g but that isn't a default.

mcpherrinm··on The difficulty of making sure your website is broken
Yeah, Chrome only partly supports revocation (Not sure exactly the criteria, but our test sites don't match it).
mcpherrinm··on Git commands I run before reading any code
Git bisect is one of the important reasons IMO to always squash-merge pull requests: Because the unit of review is the pull request.

I think this is all Github's fault, in the end, but I think we need to get Github to change and until then will keep using squash-merges.

mcpherrinm··on Git commands I run before reading any code
Squash merge is the only reasonable way to use GitHub:

If you update a PR with review feedback, you shouldn’t change existing commits because GitHub’s tools for showing you what has changed since your last review assume you are pushing new commits.

But then you don’t want those multiple commits addressing PR feedback to merge as they’re noise.

So sure, there’s workflows with Git that doesn’t need squashing. But they’re incompatible with GitHub, which is at least where I keep my code today.

Is it perfect? No. But neither is git, and I live in the world I am given.

mcpherrinm··on Woman who never stopped updating her lost dog's chip reunites with him after 11y
Yes, it's just a number referenced in one of a few databases.

> The 15-digit pet microchip is the international standard (see ISO 11784:1996 and ISO 11785:1996)

https://www.aaha.org/for-veterinary-professionals/microchip-...

https://en.wikipedia.org/wiki/ISO_11784_and_ISO_11785

mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
It does mean Unix timestamps. The blog post doesn’t have the full details.

You can read the RFC draft at https://datatracker.ietf.org/doc/html/draft-ietf-acme-dns-pe...

It says: CAs MUST properly parse and interpret the integer timestamp value as a UNIX timestamp (the number of seconds since 1970-01-01T00:00:00Z ignoring leap seconds) and apply the expiration correctly.

mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
Note that we only do best-effort submission of final certs, so it's not actually guaranteed that they end up being logged.
mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
Two current mitigations and one future:

DNSSEC prevents any modification of records, but isn’t widely deployed.

We query authoritative nameservers directly from at least four places, over a diverse set of network connections, from multiple parts of the world. This (called MPIC) makes interception more difficult.

We are also working on DNS over secure transports to authoritative nameservers, for cases where DNSSEC isn’t or won’t be deployed.

mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
It has these primary advantages:

1. It matches what the CAA accounturi field has

2. Its consistent across an account, making it easier to set up new domains without needing to make any API calls

3. It doesn’t pin a users key, so they can rotate it without needing to update DNS records - which this method assumes is nontrivial, otherwise you’d use the classic DNS validation method

mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
This wasn’t the first version of the ballot, so there was substantial work to get consensus on a ballot before the vote.

CAs were already doing something like this (CNAME to a dns server controlled by the CA), so there was interest from everyone involved to standardize and decide on what the rules should be.

mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
We (Let’s Encrypt) also agree 10 days seems too long, so we are migrating to 7 hours, aligning with the restrictions on CAA records.
mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
Yes, you can limit both challenge types and account URIs in CAA records.

To revoke the record, delete it from DNS. Let’s Encrypt queries authoritative nameservers with caches capped at 1 minute. Authorizations that have succeeded will soon be capped at 7 hours, though that’s independent of this challenge.

mcpherrinm··on DNS-Persist-01: A New Model for DNS-Based Challenge Validation
There is no username in ACME besides the account URI, so the UUID you’re suggesting isn’t needed. The account uri themselves just have a number (db primary key).

If you’re worried about correlating between domains, then yes just make multiple accounts.

There is an email field in ACME account registration but we don’t persist that since we dropped sending expiry emails.

mcpherrinm··on The Day the Telnet Died
As I understand it, greynoise is monitoring scanner traffic, so yes this would all be scans or attacks
mcpherrinm··on Upcoming changes to Let's Encrypt and how they affect XMPP server operators
The current PKI system was designed by Netscape as part of SSL to enable secure connections to websites. It was never independent of the web. Of course PKIs and TLS have expanded beyond that.

"WebPKI" is the term used to refer to the PKI used by the web, with root stores managed by the browsers. Let's Encrypt is a WebPKI CA.

mcpherrinm··on 6-Day and IP Address Certificates Are Generally Available
The "client cert" requirements were specifically not a CABF rule because that would rule it out for everyone complying with those rules, which is much broader than just the CAs included in Chrome.

Some CAs will continue to run PKIs which support client certs, for use outside of Chrome.

In general, the "baseline requirements" are intended to be just that: A shared baseline that is met by everyone. All the major root programs today have requirements which are unique to their program.

mcpherrinm··on 6-Day and IP Address Certificates Are Generally Available
This is a two-sided solution, and one significant reason for shorter certificate lifetimes helps make revocation work better.
mcpherrinm··on 6-Day and IP Address Certificates Are Generally Available
I chose 160 hours.

The CA/B Forum defines a "short-lived" certificate as 7 days, which has some reduced requirements on revocation that we want. That time, in turn, was chosen based on previous requirements on OCSP responses.

We chose a value that's under the maximum, which we do in general, to make sure we have some wiggle room. https://bugzilla.mozilla.org/show_bug.cgi?id=1715455 is one example of why.

Those are based on a rough idea that responding to any incident (outage, etc) might take a day or two, so (assuming renewal of certificate or OCSP response midway through lifetime) you need at least 2 days for incident response + another day to resign everything, so your lifetime needs to be at least 6 days, and then the requirement is rounded up to another day (to allow the wiggle, as previously mentioned).

Plus, in general, we don't want to align to things like days or weeks or months, or else you can get "resonant frequency" type problems.

We've always struggled with people doing things like renewing on a cronjob at midnight on the 1st monday of the month, which leads to huge traffic surges. I spend more time than I'd like convincing people to update their cronjobs to run at a randomized time.

mcpherrinm··on 6-Day and IP Address Certificates Are Generally Available
Some ACME clients that I think currently support IP addresses are acme.sh, lego, traefik, acmez, caddy, and cert-manager. Certbot support should hopefully land pretty soon.
mcpherrinm··on Design and Implementation of Sprites
I'm sure this is a difference-of-learning or whatever, but I'm usually unwilling to try a product until I can understand it and how it works from the documentation
mcpherrinm··on NIST was 5 μs off UTC after last week's power cut
You can look at who the "Stratum 2" servers are, in the NTP.org pool and otherwise. Those are servers who sync from Stratum 1, like NIST.

Anyone can join the NTP.org pool so it's hard to make blanket statements about it. I believe there's some monitoring of servers in the pool but I don't know the details.

For example, Ubuntu systems point to their Stratum 2 timeservers by default, and I'd have to imagine that NIST is probably one of their upstreams.

An NTP server usually has multiple upstream sources and can steer its clock to minimize the error across multiple servers, as well as detecting misbehaving servers and reject them ("Falseticker"). Different NTP server implementations might do this a bit differently.

mcpherrinm··on Upcoming Changes to Let's Encrypt Certificates
Hm, it's supposed to be https://letsencrypt.org/docs/integration-guide/ - but it looks like the link is broken. I'll fix it.
mcpherrinm··on Upcoming Changes to Let's Encrypt Certificates
It was actually outside of my small apartment with bad lighting
mcpherrinm··on 10 Years of Let's Encrypt
We’ve already started drafting it :)
mcpherrinm··on 10 Years of Let's Encrypt
Let’s Encrypt does operate CT logs. I wrote a blog post about our current-generation logs at https://letsencrypt.org/2024/03/14/introducing-sunlight
mcpherrinm··on 10 Years of Let's Encrypt
Let’s Encrypt currently has a single primary with a handful of replicas, split across a primary and backup DC.

We’re in progress of adopting Vitess to shard into a handful of smaller instances, as our single big database is getting unwieldy.

← PreviousPage 2 of 34Next →