check_ssl_cert
certspotter
| check_ssl_cert | certspotter | |
|---|---|---|
| 4 | 4 | |
| 355 | 918 | |
| - | 1.1% | |
| 8.8 | 6.9 | |
| 18 days ago | about 1 month ago | |
| Shell | Go | |
| GNU General Public License v3.0 only | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
check_ssl_cert
-
Encrypted traffic interception on Hetzner and Linode targeting Jabber service
https://github.com/matteocorti/check_ssl_cert
- Find Expiring SSL Certs using curl, Go and Perl
-
Never have an SSL certificate expire again
Wouldn't it be easier to just put it in your existing monitoring system?
* https://github.com/matteocorti/check_ssl_cert
* https://exchange.nagios.org/directory/Plugins/Network-Protoc...
- SSL error detection/expire bash script
certspotter
- SSLMate/Certspotter: Certificate Transparency Log Monitor
-
Last Chance to Fix EIDAS (Mozilla)
> 1. Is this proactively monitored for? And how? And by whom?
Yes, security researchers and domain owners use Certificate Transparency Monitors to search for certificates. e.g.:
https://crt.sh/ - allows you to search for certificates for a domain
https://github.com/SSLMate/certspotter/ - open source tool which notifies you when a certificate is issued for one of your domains
https://sslmate.com/certspotter/ - commercial service that does the same, operated by my company
> 2. If a major state-level CA was discovered to have issued a mitm cert, would browser vendors really take the commercial hit of removing or distrusting their root cert?
In 2017, Chrome and Firefox distrusted Symantec, which was at the time the world's largest certificate authority: https://security.googleblog.com/2017/09/chromes-plan-to-dist...
Symantec hadn't even issued MitM certs - they were just grossly incompetent. Distrusting them was very painful, but necessary to upload the integrity of the CA system, and demonstrated conclusively that there is no such thing as a too-big-to-fail CA.
-
Encrypted traffic interception on Hetzner and Linode targeting Jabber service
Indeed, a CT monitor which sends alerts about legitimate certificates is pretty much useless due to noise. My service, Cert Spotter, provides an API endpoint[1] which you can upload your CSRs to, so you don't get alerted about certificates using the same key as the CSR. The open source version of Cert Spotter can invoke a script[2] when a certificate is discovered, and the script can cross reference against a list of legitimate certs.
[1] https://sslmate.com/help/reference/certspotter_authorization...
[2] https://github.com/SSLMate/certspotter/blob/master/man/certs...
- Google's Certificate Transparency Search page to be discontinued May 15th, 2022
What are some alternatives?
Revssl - A script that automates generation of OpenSSL reverse shells
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
osv.dev - Open source vulnerability DB and triage service.
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.
acmetool - :lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt)
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
rap - Raspberry Pi RIPE Atlas Probe
NPushOver - Full fledged, async, .Net Pushover client
certificate-transparency-go - Auditing for TLS certificates (Go code)
https-portal - A fully automated HTTPS server powered by Nginx, Let's Encrypt and Docker.