Aaron Toponce atoponce

Top-500 Commonly Used Passwords

This table shows passwords which come from Mark Burnett's 10 million password dump, picking only the top 500. Each password is checked against our strength testers.

See the public Gist of atoponce/password_strength.md about a description of each generator and the strength tester.

Randomly Generated Passwords

This table shows passwords generated from a number of different generetors of different strengths,and their results using different strength testing checkers.

See the public Gist of atoponce/password_strength.md about a description of each generator and the strength tester.

Open Source Password Generator / Strength Meter Testing

This is a collection of password generators and strength meter testing. Each generator produces a different array of passwords, of which are then tested against each of the strength meters. The defaults are used where possible, otherwise sane options are provided.

The Results

The following results are tables showing the generators, passwords, and strength testers described below.

Randomly generaterd passwords: atoponce/random_results_table.md

Strongly Recommended

Disable DCC

/plugin unload xfer
/set weechat.plugin.autoload *,!xfer

Disable CTCP

/set irc.ctcp.action ""
/set irc.ctcp.clientinfo ""
/set irc.ctcp.finger ""

/set irc.ctcp.ping ""

Below is the starting tweet for each thread of #CipherMysteries. 32 total ciphers will be discussed. When all 32 are tweeted, a post at my blog (https://pthree.org) will be written discussing each of the 32 at length.

Introduction

This allows you to use Vim as a secure password manager. It was inspired and mostly lifted from http://pig-monkey.com/2013/04/password-management-vim-gnupg/. It differs in that a specification is now defined, and a syntax highlighting file is provided to highlight keywords and hide passwords. Additionally, this Gist uses *.pw file extensions to trigger the syntax highlighting, in addition to some custom GPG config.

GnuPG.vim

Save in ~/.vim/plugin/gnupg.vim. Grab from https://github.com/jamessan/vim-gnupg.

Vimrc

Save in ~/.vimrc:

if has("autocmd")

Documentation Standards

When creating documentation for your project, you should take advantage of some standards defined by the IETF for metasyntactic variables, domain names and IP addresses. Then, if people automatically copy and paste your examples, nothing harmful can (SHOULD!) happen.

Metasyntactic Variables

RFC 3092 was created on April 1 as a joke (as most RFCs created on that day are). However, there is sane logic to using standardized variables in code examples when documenting an open source project, or providing examples of how or how not to do some concept.

The variables are listed as follows:

foo
bar

	// Citation: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/random

	/*
	* Getting a random number from [0, max)
	*/

	// DO THIS (unbiased)
	function getRandomInt(max) {
	var low = (-max >>> 0) % max;
	do { var n = Math.random() * 0x100000000 >>> 0; } while(n < low);

	-----BEGIN PGP SIGNED MESSAGE-----
	Hash: SHA512

	# This word list has included material from the JMdict (EDICT, etc.)
	# dictionary files in accordance with the licence provisions of the
	# Electronic Dictionaries Research Group, and is covered under their
	# Creative Commons Attribution-ShareAlike Licence.
	#
	# http://www.edrdg.org/edrdg/licence.html
	#

	shuff() {
	if [ $(command -v shuf) ]; then
	shuf -n "$1"
	elif [ $(command -v shuffle) ]; then
	shuffle -f /dev/stdin -p "$1"
	else
	awk 'BEGIN{
	"od -tu4 -N4 -A n /dev/urandom" \| getline
	srand(0+$0)
	}