- Nmap. The script requires version 6.25 or newer. The latest version, 6.46, already includes the next 2 dependencies, so you can skip directly to the Scanning section below.
- An easy way to get the latest Nmap release is to use Kali Linux.
- Binary installers are available for Windows.
- RPM installer available for Linux, or install from source.
- .dmg installer available for Mac OS X.
- tls.lua. The script requires this Lua library for TLS handshaking.
- ssl-heartbleed.nse. This is the script itself.
nsa-yoda
/ NmapHeartbleed.md
Created
July 31, 2014 14:38
— forked from bonsaiviking/NmapHeartbleed.md
nsa-yoda
/ benchmark+go+nginx.md
Created
January 31, 2014 22:04
— forked from hgfischer/benchmark+go+nginx.md
There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.
So, these are the different settings we are going to compare:
- Go HTTP standalone (as the control group)
- Nginx proxy to Go HTTP
- Nginx fastcgi to Go TCP FastCGI
- Nginx fastcgi to Go Unix Socket FastCGI