Mick micksmix

Cryptographic Best Practices

Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.

The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from

	#!/bin/bash
	#Script to Scan All Sites Found With A Simple NMAP Scan With Burp.

	sites=$(nmap "$1" --open 443 --resolve-all --open -oG - \| awk 'NR!=1 && /open/{print $2}')

	for site in $sites
	do
	curl -vgw "\\n" 'http://127.0.0.1:1337/v0.1/scan' -d '{"urls":["'"$site"'"]}' > /dev/null 2>&1
	printf "Scanning %s with burp.\\n" "$site"
	done

 # ag <https://github.com/ggreer/the_silver_searcher>
 # usage: ag-replace.sh [search] [replace]
 # caveats: will choke if either arguments contain a forward slash
 # notes: will back up changed files to *.bak files
 ag -0 -l $1 | xargs -0 perl -pi.bak -e "s/$1/$2/g"
 # or if you prefer sed's regex syntax:
 ag -0 -l $1 | xargs -0 sed -ri.bak -e "s/$1/$2/g"