Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/client9/sslassert
simple scripts to make sure your web server is configured correctly under HTTPS
https://github.com/client9/sslassert
Last synced: about 2 months ago
JSON representation
simple scripts to make sure your web server is configured correctly under HTTPS
- Host: GitHub
- URL: https://github.com/client9/sslassert
- Owner: client9
- Created: 2013-07-12T07:19:44.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2013-10-01T10:32:55.000Z (almost 11 years ago)
- Last Synced: 2024-05-08T17:14:47.738Z (4 months ago)
- Language: CSS
- Homepage:
- Size: 422 KB
- Stars: 57
- Watchers: 7
- Forks: 9
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-starred - client9/sslassert - simple scripts to make sure your web server is configured correctly under HTTPS (others)
README
sslassert
==============
Simple unit tests to make sure your web server is configured correctly under SSL.
It's in `sh` (subset of `bash`). Why? It's one file, no
installation, only requires openssl, and basic posix shell stuff. And
mostly it's calling out to OpenSSL anyways, so why not bash?
sslfacts
--------------
```
export HOSTPORT=www.google.com
export URLPATH=/
source sslassert.sh
```
Will then generate a number of facts based on the site:
* accepted and rejected cipher suites
* protocol support for sslv2 - tls1.2
* various statistics on symmetric and public key cryptography
* various certificate facts
* common problems and attacks
You can see the full fact list by running the sample script
```
./sslfact.sh libinjection.client9.com
```
sslassert
---------------
Then you'll want to test the facts against what your expectations.
The same script below shows how. You can use any of the bash test
operators (e.g. -gt,-ge,-lt,-le,-ne,-eq, =, !=, > etc)
```
#!/bin/sh
export HOSTPORT=www.google.com
export URLPATH=/
source sslassert.sh
sslassert 'secure-renegotiation = on'
sslassert 'compression = off'
sslassert 'certificate-length -ge 1024'
sslassert 'protocol-ssl-v2 = off'
sslassert 'protocol-tls-v12 = on'
sslassert 'crypto-weak = off'
sslassert 'beast-attack = off'
exit $SSLASSERT_EXIT
```
and that's it.
Note for later reference:
Certificate chain is not self-signed
------------------------------------
```
Certificate chain
0 s:/OU=Domain Control Validated/CN=YOUR SERVER HERE
i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=1234
1 s:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=1234
i:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
2 s:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
i:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
```
Looking at #2 in the chain, you'll see a self-signed cert for
Go-Daddy. That's normally inside the http-client already, so sending
it is kinda weird, and might cause problems. It's certainly a waste
of space.