惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
Microsoft Azure Blog
Microsoft Azure Blog
aimingoo的专栏
aimingoo的专栏
Vercel News
Vercel News
U
Unit 42
L
LangChain Blog
J
Java Code Geeks
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog
F
Fortinet All Blogs
小众软件
小众软件
I
InfoQ
P
Proofpoint News Feed
D
DataBreaches.Net
Martin Fowler
Martin Fowler
H
Help Net Security
T
Tailwind CSS Blog
N
Netflix TechBlog - Medium
有赞技术团队
有赞技术团队
Y
Y Combinator Blog
Recent Announcements
Recent Announcements
B
Blog RSS Feed
酷 壳 – CoolShell
酷 壳 – CoolShell
B
Blog

Let's Encrypt Community Support - Latest posts

Fail to renew NGINX cert Installing across 2 servers Transitioning to 45-day certs: How to handle certificates with >25 SANs (blocked by `tlsserver` limit) TSplus certificate installation error Certsage Urn:ietf:params:acme:error:malformed [Let's Encrypt Blog] A Post-Quantum Future for Let's Encrypt Guidance on Security Review for Let’s Encrypt Adoption 2026.06.03 CRLs Temporarily Missing Revoked Serials ACME 404 errors for existing end-to-end tests: “No such authorization” / “Certificate not found” Certbot fullchain missing intermediates Can't generate certificate - Unable to validate JWS Unable to renew certificate on RHEL 8 Lost where my certificate is renewed from Want get R13 (ISRG Root X1) with acme.sh or certbot script Error renewing certificates, Error finalizing order :: authorizations for these identifiers not found: Error getting certificates ACME 404 errors for existing end-to-end tests: “No such authorization” / “Certificate not found” Certificate creation failed with message [Fail to load resource from 'https://acme-v02.api.letsencrypt.org/acme/finalize/ SSL certificate expired Certbot Code 1, Installing AMP for MC on CachyOS Certonly --force-renewal Need newby help with getting cert for my nas with my zip file Creating ssl certificate synology IKEv2 (strongSwan) fails with Let's Encrypt YR2 chain (works with other servers / chain mismatch suspected) Client can't connect ikev2 server HTTP-01 and AWS challenge Trouble with dns-rfc2136 plugin Getssl hangs, Lets Encrypt not requesting token Has there been a recent change in order/authorization reuse behavior for the Classic profile? Invalid response from web address so cannot validate
ISRG may have received a National Security Letter or FISA...
petercooperj · 2026-04-22 · via Let's Encrypt Community Support - Latest posts
Not sure if this is really something to be concerned about or just absolutely nothing, but I thought it would be worthwhile to note it for the record and for visibility: The recently-released ISRG Legal Transparency Report for the second half of 2025 says in the "National security process" line a number of "0-249". The description of that line says that: What we can say about either FISA court orders or NSL that we receive is highly regulated, and depends on exactly how we report the information. Current guidelines on reporting, codified as part of the USA FREEDOM Act, allow companies to disclose the combined number of NSLs and both content and non-content FISA orders as a single number in bands of 250, starting with 0-249. So that may mean that they received 0, or it may mean that they received any number less than 250. However, if you look at their previous transparency reports , the number was always specifically reported as "0" rather than "0-249". I don't know if that means that they were always supposed to be reporting the range previously even if it were 0, or if it means something changed and the number is now specifically indicated as being something greater than 0. Again, may mean nothing, and even if they did have to comply with something relating to that "National security process" it may not necessarily mean anything especially nefarious. Just noting it as a change in what was recorded in the transparency report. 2 posts - 2 participants Read full topic