CertKit SSL Certificate Automation

CertKit SSL Certificate Automation

@certkit.io

Automated SSL certificate management for IT teams who have better things to do. No scripts, no cron jobs. Free 90-day trial to start renewing your certificates. Learn more at https://www.certkit.io/

32 followers28 following112 posts

Starting tomorrow, Chrome shows NET::ERR_CERT_AUTHORITY_INVALID for InCommon SSL certificates on eMudhra's ECC root. 3,134 at 41 schools still chain to it. Skip eMudhra RSA, it's leaving too. Move once: www.certkit.io/blog/incommo... #PKI #SSL

certkit.ioFixing distrusted InCommon certificates with ERR_CERT_AUTHORITY_INVALIDInCommon's G3C certificates fail in Chrome with ERR_CERT_AUTHORITY_INVALID starting October 27, and moving them to another CA is the fix that lasts.

Chrome stops trusting eMudhra's ECC root Tuesday. And eMudhra is leaving the TLS business, so InCommon certificates reissued on its RSA chain will have to move again. Move once. We can help this weekend. www.certkit.io/blog/emudhra... #PKI #SSL

certkit.ioInternet2's certificate authority (eMudhra) is being distrustedeMudhra, the CA behind Internet2's InCommon certificates, made trivially simple keys, and Chrome drops its ECC root and 30,000 certificates October 27.

CertKit SSL Certificate Automation reposted

Probably the hardest part of explaining the impact of the eMudhra certificate kerfuffle was working out exactly how many things an enterprise has to update when the chain of trust stops being trustworthy; second hardest was keeping up with eMudhra's explanations and in the end, they just gave up

thestack.technologyeMudhra's certificate blunder leaves enterprises with a lot of cleanupFrom FIPS to facepalm; when the chain of trust is compromised, everything that uses certificates for that trust has to be checked and updated – and that means everything.

CertKit SSL Certificate Automation reposted

turns out eMudhra - which just got out of the cert business altogether - isn't just a problem for Indian customers; the G3 root that signed the dodgy keys, that Firefox already distrusts, that Google will distrust on the 27th is what a bunch of US university certs chain up to

Last night 43 of 57 large universities still had current certs on that chain. Minnesota, Michigan, Washington and UC San Diego had 500+ each. I just published our writeup on it. www.certkit.io/blog/emudhra...

-----BEGIN EC PRIVATE KEY----- 4 -----END EC PRIVATE KEY----- That's they key behind Internet2's InCommon SSL. The root gets distrusted on Tuesday, and about 30K certificates need to get replaced. www.certkit.io/blog/emudhra... #PKI #SSL

certkit.ioInternet2's certificate authority (eMudhra) is being distrustedeMudhra, the CA behind Internet2's InCommon certificates, made trivially simple keys, and Chrome drops its ECC root and 30,000 certificates October 27.

Check any server's SSL certificate chain and post-quantum readiness with our free tools. No account needed. As of today, CertKit monitoring runs the same checks on your hosts, alongside expiry. www.certkit.io/blog/certifi... #TLS #PQC

certkit.ioCertificate monitoring with TLS, chain, and post-quantum readinessCertKit's SSL certificate monitoring now grades every host's certificate chain, TLS versions, and post-quantum key exchange, along with the expiry date.

"Where is the SSL certificate for examplecom?" is now one search across every client you manage. New in CertKit: cross-collection search, a dashboard with a 90-day renewal timeline, and a read-only API for dashboards and invoices. www.certkit.io/blog/certkit...

certkit.ioCertKit for MSPs: a new dashboard, search everywhere, and the APIEvery collection and client on one page, a search that finds any certificate, host, or agent, a new dashboard, and a read-only API for the rest.

Apple's draft policy for Merkle Tree Certificates caps validity at 7 days. Not a shorter X.509. A new post-quantum cert type, validated from periodic out-of-band client updates, so it only has to outlive the update cycle. 7 days costs nothing when nothing human renews it. #PKI

Some jerk got an SSL certificate for a subdomain we had forgotten about, and Google told us before our own CT log tool did. Now CertKit watches the log. You get an email when a certificate shows up for a name it has never seen on your domain. www.certkit.io/blog/ct-alerts

certkit.ioCT alerts: know when someone gets a certificate for your domainsCertKit now watches certificate transparency logs for your domains and emails you when a certificate appears that you have never seen before.

We're in the Japanese celebrity gossip site business now. A DNS record we forgot for ten years pointed at an IP we gave up. Some jerk got the IP, a Let's Encrypt cert, and a spam site The cert sat in our own CT tool the whole time. www.certkit.io/blog/danglin...

certkit.ioHow a ten-year-old dangling DNS record handed one of our subdomains to spammersWe forgot a DNS record for ten years. Someone else got the IP, a certificate, and our subdomain. How dangling DNS becomes a subdomain takeover.

Cloud SSL certificate monitoring only sees what the internet sees. Your intranet pages expire too, but they don't warn anyone first. CertKit agents now monitor SSL certificates inside your network, and judge trust from the host's own trust store. www.certkit.io/blog/certifi... #PKI #sysadmin

certkit.ioCertificate monitoring for your intranet hostsCertKit agents now monitor TLS endpoints inside your network, judge trust from the host's trust store, and re-check hosts the moment a certificate deploys.

A 47-day SSL certificate is not a shorter version of the same job. It is a different job. Once a year, a person can renew it. Eight times a year, they cannot. Issuance was solved. Distribution is the hard part. runasradio.com/Shows/Show/1... #SSL #SysAdmin

runasradio.com47 Day Certificates with Todd GardnerThe 47-day certificate is coming! While at NDC in Toronto, Richard received an update from Todd Gardner about his show last year: certificate authorities are moving toward SSL certificates that last o...

Why are SSL certificates dropping to 47 days? Because revocation is broken. OCSP fails open. Revocation lists go stale. A stolen certificate stays trusted too long. Short lifespans are the industry's workaround. runasradio.com/Shows/Show/1... #SSL #InfoSec

runasradio.com47 Day Certificates with Todd GardnerThe 47-day certificate is coming! While at NDC in Toronto, Richard received an update from Todd Gardner about his show last year: certificate authorities are moving toward SSL certificates that last o...

PKI has a term for the leaf-to-root trust chain. It has no term for the series of certs you've been renewing for years. Certbot calls it a lineage. Nobody else picked it up. At 47-day lifetimes, naming this correctly starts to matter. www.certkit.io/blog/certifi... #PKI #TLS

certkit.ioCertificate lineage: the concept your tools already use but nobody namedPKI has precise terminology for almost everything. The one thing it never named is the series of certificates you've been renewing for years. Here's what it is, why it matters now, and why your tools ...

Apple's 398-day limit exempts private CAs. Most people stopped reading there. There's a second Apple requirement: all TLS certs, 825 days max. Safari silently rejects anything longer. No bypass, no details. www.certkit.io/blog/apple-d... #PrivatePKI #PKI

certkit.ioApple doesn't care who signed your certificateRunning a private CA to escape the public cert treadmill makes sense. Apple still enforces an 825-day validity limit in Safari on every TLS certificate, no matter who issued it.

PSA: You don't need a private CA for internal SSL certificates. DNS-01 ACME challenges let you issue publicly trusted certs for servers that never touch the internet. No root cert distribution. No click-through warnings. www.certkit.io/blog/private... #PKI #SSL

certkit.ioYou probably don't need private PKI for internal infrastructureMost teams assume internal infrastructure needs a private CA. It doesn't - and skipping it saves you from a maintenance burden that never fully works anyway.

When your auditor asks what happened to your certificates last Tuesday, you need an answer. CertKit now logs every action in your certificate lifecycle: issuances, renewals, revocations, deployments, agent approvals. With importance flags so you can find what matters. #CertificateManagement #PKI

F5 LTM. Palo Alto. Azure Key Vault. Exchange. We shipped a deployment scripting template library for all of them. Pick your target, configure your variables, and CertKit pushes the certificate to your infrastructure. www.certkit.io/blog/deploym... #CertificateManagement #PKI

certkit.ioRemote deployment scriptingCertKit now ships centrally managed deployment scripts that push certificates directly to appliances, cloud platforms, and custom infrastructure, with a template library and encrypted variable storage...

50 SSL certificates managed manually today means roughly 50 renewals a year. Same team, same certs, in 2029: 400. The CA/Browser Forum's new lifetime schedule doesn't just change how often you renew. It changes the job. www.certkit.io/blog/shrinki... #PKI #SSL

certkit.ioCertificate lifetimes are shrinking.Certificate validity is dropping from 398 days to 47 days by 2029. Here is the canonical schedule, what's driving it, and what it does to your renewal workload.

Managing SSL certs across dozens of servers? You shouldn't have to configure each one by hand. New in CertKit: copy and link agent configs across your fleet, search and filter your monitors, plus our first GDPR Data Processing Agreement. www.certkit.io/blog/shared-... #CertificateManagement #SSL

certkit.ioShared agent configs, monitor search, and a GDPR policyCopy and share agent configurations across your fleet, search and sort your monitored domains, and our first official Data Processing Agreement for GDPR compliance.