ssh-audit
testssl.sh
Our great sponsors
| ssh-audit | testssl.sh | |
|---|---|---|
| 21 | 43 | |
| 3,133 | 7,647 | |
| - | - | |
| 8.6 | 8.7 | |
| 5 days ago | 2 days ago | |
| Python | Shell | |
| MIT License | GNU General Public License v3.0 only |
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.
ssh-audit
-
Terrapin Attack for prefix injection in SSH
No. Mitigations are available now. Follow the recommendations from ssh-audit (master version). [0]
0. https://github.com/jtesta/ssh-audit
- SSH-audit: SSH server and client security auditing
- Quick/simple question checking for SSH vulnerabilities
- Why so many bots?
-
How to secure my self-hosted website?
Match Address 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 PasswordAuthentication yes ```` You may audit your SSH service by https://github.com/jtesta/ssh-audit
-
Why does my SSH private key still work after changing some bytes? (2016)
Off topic: audit tool for OpenSSH config files.
Posted here because SSH algorithms are a moving target.
https://github.com/jtesta/ssh-audit/tree/e50ac5c84d46e902e02...
-
SFTP (SSH) Cipher Sanity Check
In addition to ssllabs, I'll recommend jtesta's ssh-audit.py
testssl.sh
-
Badssl.com
You’re in luck because such a tool exists :) https://testssl.sh/
- Testing TLS/SSL Encryption
-
Uncertain how to proceed with patching SSL and TLS issues in MacOS (Sweet32)
Run https://testssl.sh/ and see what ciphers are being offered.
-
Changing SSL Wildcard Certificate
There is https://github.com/drwetter/testssl.sh utility. It can help diagnose issues (e.g. diffs between working and non-working sites).
- Specific SSL Ciphers Test
-
SSL Diag Tool
For internal use, there's https://testssl.sh/
-
Dovecot not offering TLSv1.2 after a few minutes
The current configuration allows for TLSv1 to TLSv1.3 connections. I can verify those using testssl.sh, the tests will succeed (although correctly mentioning, that TLSv1 and TLSv1.1 should be disabled). Running the tests again after about 5 minutes, the results are different. TLSv1.2 now shows "not offered and downgraded to a weaker protocol".
- How to combine pem file and 3 security certificates?
- oggi 2022-11-01 verrà rilasciata una vulnerabilità di livello CRITICAL su OpenSSL 3.0.x
-
alternative to whatsmychaincert.com cli or gui
testssl.sh
What are some alternatives?
Pritunl - Enterprise VPN server
https-ssl-cert-check-zabbix - Script to check validity and expiration of TLS/SSL certificate on hosts. May be used with Zabbix or standalone.
yubikey-agent - yubikey-agent is a seamless ssh-agent for YubiKeys.
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way. No scripts.
ufw-docker - To fix the Docker and UFW security flaw without disabling iptables
ssh-audit - SSH server auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc)
tinyssh - TinySSH is small server (less than 100000 words of code)
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
mistborn
OpenSSL - TLS/SSL and crypto library
easy-admin - Scripts for easy system administration
f5-azure-arm-templates - Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure