Javier Junquera Sánchez junquera

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

Generic makefile example for a C++ project

If you need a small makefile introduction/reference you can take a look at my notes https://www.mauriciopoppe.com/notes/os/bin/make/

Project structure

. project
├── Makefile
├── build


	########## Install NGINX ##############

	# Install software-properties-common package to give us add-apt-repository package
	sudo apt-get install -y software-properties-common

	# Install latest nginx version from community maintained ppa
	sudo add-apt-repository ppa:nginx/stable

	# Update packages after adding ppa

	import os
	import re
	import sys
	import logging
	import argparse
	import subprocess

	import requests

	# Exploit Author: Juan Sacco at KPN Red Team
	# Developed using Exploit Pack - http://www.exploitpack.com <[email protected]>
	#
	# Description: Microsoft Word (CVE-2017-0199) is prone to a RCE trough a HTA Handler
	# A remote code execution vulnerability exists in the way that Microsoft Office and WordPad parse specially crafted files.
	# An attacker who successfully exploited this vulnerability could take control of an affected system.
	#
	# Impact: An attacker could exploit this vulnerability to execute arbitrary commands in the
	# context of the application. Failed exploit attempts could result in a
	# denial-of-service condition.

	from bs4 import BeautifulSoup
	import requests

	import time
	import sys
	import os

	from selenium import webdriver
	from selenium.webdriver.common.keys import Keys

	#!/bin/sh

	for i in `cowsay -l \| tail -n +2`
	do
	echo $i
	cowsay -f $i "Ich bin die Kuh"
	sleep 3
	done

	Commit your changes.

	Inspect your package.json file to check your current version number, and decide (if your package.json shows version 2.1.0):

	- Register your package on atom.io

	> apm login


	1- You want to make a patch version release

	import sys
	import argparse

	import stem
	from stem.control import Controller

	def main():

	parser = argparse.ArgumentParser(description="%s fetches a Tor hidden "
	"service descriptor." % sys.argv[0])

	import hashlib
	import base64
	import argparse
	import sys

	from Crypto.PublicKey import RSA


	def calculate_onion(pem_key):
	key = RSA.importKey(pem_key)