Carlos Soria cultome

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

	require 'ed25519'

	payload = 'plain text'

	# generate key pair
	signing_key = Ed25519::SigningKey.generate
	verify_key = signing_key.verify_key
	p signing_key
	p verify_key

	# content has to be in .config/fish/config.fish
	# if it does not exist, create the file
	setenv SSH_ENV $HOME/.ssh/environment

	function start_agent
	echo "Initializing new SSH agent ..."
	ssh-agent -c \| sed 's/^echo/#echo/' > $SSH_ENV
	echo "succeeded"
	chmod 600 $SSH_ENV
	. $SSH_ENV > /dev/null

	<?php

	use Swagger\Annotations as SWG;

	/**
	* @SWG\Swagger(
	* basePath="/v1",
	* host="api.local",
	* schemes={"http"},
	* produces={"application/json"},

	/**
	* I couldn't find a super simple example of how to run Karma, PhantomJs, with
	* Jasmine tests via npm, so eventually I decided to create my own. Maybe
	* someone will find it useful.
	*
	*
	* Installation (using npm):
	*
	* npm install -g karma-cli
	* npm install -g karma --save-dev

	# Signal catching
	def shut_down
	puts "\nShutting down gracefully..."
	sleep 1
	end

	puts "I have PID #{Process.pid}"

	# Trap ^C
	Signal.trap("INT") {

	<?php

	// API access key from Google API's Console
	define( 'API_ACCESS_KEY', 'YOUR-API-ACCESS-KEY-GOES-HERE' );


	$registrationIds = array( $_GET['id'] );

	// prep the bundle
	$msg = array

	require 'faraday'
	require 'zlib'

	module FaradayMiddleware
	class Gzip < Faraday::Response::Middleware

	def on_complete(env)
	encoding = env[:response_headers]['content-encoding'].to_s.downcase
	case encoding
	when 'gzip'

	Latency Comparison Numbers (~2012)
	----------------------------------
	L1 cache reference 0.5 ns
	Branch mispredict 5 ns
	L2 cache reference 7 ns 14x L1 cache
	Mutex lock/unlock 25 ns
	Main memory reference 100 ns 20x L2 cache, 200x L1 cache
	Compress 1K bytes with Zippy 3,000 ns 3 us
	Send 1K bytes over 1 Gbps network 10,000 ns 10 us
	Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD