skratchdot

A list of some other badges: http://shields.io/

Version Numbers

Alt Text	Image Src	Link
NPM version	https://badge.fury.io/{{programming_language:js}}/{{project_name}}.svg	http://badge.fury.io/{{programming_language:js}}/{{project_name}}
Dependency Status	https://david-dm.org/{{username}}/{{project_name}}.svg	https://david-dm.org/{{username}}/{{project_name}}
devDependency Status	https://david-dm.org/{{username}}/{{project_name}}/dev-status.svg	https://david-dm.org/{{username}}/{{project_name}}#info=devDependencies
GEM Dependency Status	https://gemnasium.com/{{username}}/{{repo}}.png	https://gemnasium.com/{{username}}/{{repo}})

chris-rock

// Nodejs encryption with GCM
// Does not work with nodejs v0.10.31
// Part of https://github.com/chris-rock/node-crypto-examples

var crypto = require('crypto'),
  algorithm = 'aes-256-gcm',
  password = '3zTvzr3p67VC61jmV54rIYu1545x4TlY',
  // do not use a global iv for production, 
  // generate a new one for each encryption
  iv = '60iP0h6vJoEa'

martinthomson

There are two forms of QUIC common header: long and short. Long form packets are used for the initial exchange - until both 1-RTT packet protection can be started AND version negotiation is complete. Short form packets carry the bulk of the data.

This removes a lot of the flexibility that was the source of most of the objections to the current format. Fields are aligned on four octet boundaries. All long-form header variations have the exact same form. The connection ID is in the same place in both short and long form. The long form clearly identifies the role of the sender in the first octet and it identifies the