Anurag Aryan anuragcodes

Web Performance

High Performance Web Sites: Essential Knowledge for Front-End Engineers
High Performance JavaScript (Build Faster Web Application Interfaces)
Even Faster Web Sites: Performance Best Practices for Web Developers
Designing for Performance: Weighing Aesthetics and Speed

Web Design

Adaptive Web Design: Crafting Rich Experiences with Progressive Enhancement (2nd Edition) (Voices That Matter)

#Simple Authentication with Bcrypt

This tutorial is for adding authentication to a vanilla Ruby on Rails app using Bcrypt and has_secure_password.

The steps below are based on Ryan Bates's approach from Railscast #250 Authentication from Scratch (revised).

You can see the final source code here: repo. I began with a stock rails app using rails new gif_vault

##Steps

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

This is a mix between two sources:

basically the first resource is great but didn't work for me: I had to remove the trailing "/*" in the resource string to make it work. I also noticed that setting the policy on the source bucket was sufficient. In the end these are the exact steps I followed to copy data between two buckets on two accounts

Basically the idea there is:

we allowe the destination account to read the source bucket (in the console for the source account)
we log as the destination and start the copy

to create the PGP private/public key pair

https://help.github.com/articles/generating-a-new-gpg-key/

Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.

Method 1

Backup the public and secret keyrings and trust database

cp ~/.gnupg/pubring.gpg /path/to/backups/

Installing OpenSSH 7.4 on Ubuntu 16.04

sudo apt install -y build-essential libssl-dev zlib1g-dev
wget "http://mirrors.evowise.com/pub/OpenBSD/OpenSSH/portable/openssh-7.4p1.tar.gz"
tar xfz openssh-7.4p1.tar.gz
cd openssh-7.4p1
./configure
make
sudo make install

	[branch]
	autosetupmerge = true

	[core]
	editor = gedit --wait --new-window
	pager = less -x1,5
	whitespace = trailing-space,space-before-tab,tabwidth=4

	[color]
	ui = auto

	#!/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

	# module list (generated by listmodules.py)
	#
	# timestamp='20160226T200954Z'
	# sys.version='2.7.10 (default, Dec 8 2015, 18:25:23) \n[GCC 4.8.3 20140911 (Red Hat 4.8.3-9)]'
	# sys.platform='linux2'
	# platform='Linux-4.1.13-19.31.amzn1.x86_64-x86_64-with-glibc2.2.5'
	#
	BaseHTTPServer
	Bastion
	CDROM

	# Procedure is for Ubuntu 14.04 LTS.

	# Using these guides:
	# http://datacenteroverlords.com/2012/03/01/creating-your-own-ssl-certificate-authority/
	# https://turboflash.wordpress.com/2009/06/23/curl-adding-installing-trusting-new-self-signed-certificate/
	# https://jamielinux.com/articles/2013/08/act-as-your-own-certificate-authority/

	# Generate the root (GIVE IT A PASSWORD IF YOU'RE NOT AUTOMATING SIGNING!):
	openssl genrsa -aes256 -out ca.key 2048
	openssl req -new -x509 -days 7300 -key ca.key -sha256 -extensions v3_ca -out ca.crt