Viewing profile — phasmantistes
phasmantistes
HN member- Joined
- Tue, Sep 01, 2015, 4:21 PM UTC
- HN karma
- 1,065
- Public activity
- 140 items
- HN profile
- View on Hacker News ↗
About phasmantistes
Recent public activity
-
comment
Comment #48822922
The issue with saying that "there's a 60/40 split, therefore there's no consensus" is that the IETF explicitly documents that that isn't the case: RFC 7282, Section 7, "Five people…
-
comment
Comment #48822765
Sure, you make a good point. I certainly didn't expect to end up at the top of this thread, and stopped paying attention immediately after posting it (for the same reason I don't r…
-
comment
Comment #48822560
Zero percent LLM-generated, but this is the first time I've had to defend myself against that claim, so thanks for that!
-
comment
Comment #48764721
This is not an unbiased article about the situation unfolding on the TLS Working Group mailing list; this is a call to action to join one specific side of the argument that has bee…
-
comment
Comment #48081764
Our code for sending stuff to CT logs is fully open source. But that's the tiniest slice of our compliance regime -- the vast majority of it is things like audit logging certain ev…
-
comment
Comment #46285538
Yep, the "shortlived" (6-day) profile will be available to the general public later this week. But at this time we explicitly encourage only mature organizations with stable infras…
-
comment
Comment #46285527
Honest reply: because the infrastructure isn't ready to support 1-day certificates yet. If your cert is only valid for one day, and renewal fails on a Saturday, then your site is u…
-
comment
Comment #46285503
FWIW, we're acutely aware of the operational risks of super short lifetimes and frequent renewals. That's why our `shortlived` profile is clearly documented as only being appropria…
-
comment
Comment #46285442
Yep! Should be available to the general public (as long as you're using an ACME client that can be configured to request a specific profile) later this week.
-
comment
Comment #46285434
It's a good question! I know that our first root (ISRG Root X1) used that naming scheme simply because it was cross-signed by IdenTrust's root (DST Root CA X3) which used that same…
-
comment
Comment #46124366
Certificates that look like renewals -- for the same set of names, from the same account -- are exempt from rate limits. This means that renewing (for example) every 30 days instea…
-
comment
Comment #46124263
Organizations with many frontends/loadbalancers all serving the same site tend to adopt one of four solutions: - Have one node with its own ACME account. It controls key generation…
-
comment
Comment #46124075
"CT Logs" are Certificate Transparency Logs, which are cryptographically provable append-only data structures hosted by trusted operators. Every certificate issued is publicly logg…
-
comment
Comment #46124008
Please don't suggest pinning a publicly-trusted intermediate. The CA may change which intermediate they're using at any time for any reason with no warning, and then the app which …
-
comment
Comment #45969899
(Disclaimer: I am tech lead of Let's Encrypt software engineering) I'm also concerned about LE being a single point of failure for the internet! I really wish there were other free…
-
comment
Comment #44006741
That's not leverage that a CA can use. If half the internet suddenly displays TLS warning interstitials, it doesn't make people mad at the CA, and it doesn't make people mad at the…
-
comment
Comment #44006447
The "tlsclient" profile will not be TLSClientAuth-only: it will have both the TLSServerAuth and TLSClientAuth profiles, like the default profile does today. It will exist solely fo…
-
comment
Comment #42731021
This is exactly why the LE IP certs will be limited to 6 days: this exact attack is possible today against any IP address cert, and such certs in general are allowed to have lifeti…
-
comment
Comment #41051552
For what it's worth, the person you're replying to is the founder and executive director of Let's Encrypt, the non-profit free and open CA which decidedly isn't a money-printing ma…
-
comment
Comment #41048913
CAs need to know every certificate they've issued so that a) if they receive a request to revoke that certificate, they can actually do so; and b) if they need to revoke all of the…
-
comment
Comment #41048228
Not all subscribers provide email addresses through which they could be informed of a revocation.
-
comment
Comment #41048165
Nothing will change for you, and nothing will break. The point of this post is to give a maximum-lead-time heads-up to the folks who _do_ need to care (the folks writing revocation…
-
comment
Comment #39756959
I believe they are using "certbot" to mean "Let's Encrypt", in which case their advice is sound -- if you truly have to pin a key, pin your own end-entity cert's key, not the CA's …
-
comment
Comment #39756806
It's specifically to discourage intermediate key pinning. If folks want to pin their own end-entity public key (and always re-use the same key when renewing their cert), go for it …
-
comment
Comment #39716447
I'm super excited about Sunlight. The CT ecosystem is really fragile right now, with current log implemetations being expensive to operate and very difficult to operate correctly, …