atoponce

#!/usr/bin/env node

/**
 * Forked from https://gist.github.com/PaulCapestany/6148566. Changes:
 *   - Beautified code
 *   - NodeJS-specific (will not work in the browser)
 *   - Scope variables with let and const keywords
 *   - 256-bit RNG
 *   - Remove von Neumann debiasing
 *   - Remove byte assembly

atoponce

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

atoponce

#!/bin/bash
HOME=/var/services/homes/backupchef
SNAPSHOT_DIR=$HOME/backups/myserver
LOG_DIR=$HOME/backups
KEY_ID=$HOME/.ssh/id_rsa
RM=/bin/rm;
MV=/bin/mv;
CP=/bin/cp;

$RM -rf $SNAPSHOT_DIR/daily.6;                                

atoponce

#!/bin/bash
HOME=/var/services/homes/backupchef
SNAPSHOT_DIR=$HOME/backups/myserver
LOG_DIR=$HOME/backups
KEY_ID=$HOME/.ssh/id_rsa
RM=/bin/rm;
MV=/bin/mv;
CP=/bin/cp;

$RM -rf $SNAPSHOT_DIR/daily.6;                                

atoponce

#!/bin/bash
HOME=/var/services/homes/backupchef
SNAPSHOT_DIR=$HOME/backups/myserver
LOG_DIR=$HOME/backups
KEY_ID=$HOME/.ssh/id_rsa
RM=/bin/rm;
MV=/bin/mv;
CP=/bin/cp;

$RM -rf $SNAPSHOT_DIR/daily.6;