฿tcDrak btcdrak

Quick GPG Smartcard Guide

We will generate a master key with only the Certify capability and three subkeys with each of the Sign, Encrypt and Authenticate capabilities. These latter three keys are meant for daily use and will be transferred to an OpenPGP smartcard, which has three corresponding slots. The master private key can then be moved to offline cold storage, or stored on a second smartcard.

We are generating keys on a secure computer instead of on the card, because it allows more flexibility. Ideally this means a machine running Tails or one that is air-gapped and not connected to the internet.

This guide assumes that if you want to sign other peoples keys, then you will require the aforementioned secondary smartcard with your master key stored in its Signature slot, or if you only have one smartcard, then you'll have to fetch the master key out of cold storage. By default, GPG generates a master key with the Certify and

About

This is a local copy of the commands from:

This guide serves as a reference of collected information necessary for strict management of PGP keys. This includes keeping a master key that always remains

	#!/bin/bash

	# Bash script for setting or clearing touch requirements for
	# cryptographic operations the OpenPGP application on a YubiKey 4.
	#
	# Author: Alessio Di Mauro <[email protected]>

	GCA=$(which gpg-connect-agent)
	DO=0
	UIF=0

	#!/bin/bash
	# Sign a file with a private key using OpenSSL
	# Encode the signature in Base64 format
	#
	# Usage: sign <file> <private_key>
	#
	# NOTE: to generate a public/private key use the following commands:
	#
	# openssl genrsa -aes128 -passout pass:<passphrase> -out private.pem 2048
	# openssl rsa -in private.pem -passin pass:<passphrase> -pubout -out public.pem

	/*
	So you need to broadcast an alert...
	... here's what to do:

	1. Copy sendalert.cpp into your bitcoind build directory

	2. Decrypt the alert keys
	copy the decrypted file as alertkeys.h into the src/ directory.

	3. Modify the alert parameters in sendalert.cpp

	'use strict';

	var _ = require("underscore");
	var fs = require("fs");
	var Slack = require('slack-api');
	var token = "YOUR-TOKEN";

	Slack.users.list({token:token}, function (error, data) {

	// create a map with the real usernames

	using System;
	using System.Collections.Generic;
	using System.Linq;
	using System.Numerics;
	using System.Security.Cryptography;
	using System.Text;
	using System.Threading.Tasks;

	namespace Base58ReverseEncoder
	{

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

	This is a list of unspendable addresses with which to burn coins to. When you send a coin to any of these addresses, they are permanently gone and can never be redeemed.

	You can prove this by sending a small test amount to the address and then checking a block explorer or using `getrawtransaction txid 1`. You should see the coins output to somehting like `"raw_scriptPubKey": "76a914000000000000000000000000000000000000000088ac"` Some block explorers are also smart enough to indicate in their user interface that the coins were destroyed.

	You can find the version number matching to the desired altcoin by checking two places in the code:

	chainparams.cpp for bitcoin 0.9 and later based coins: