oreoshake

Current way:

1. User starts the flow
2. sudo challenge (https://github.com/blog/1513-introducing-github-sudo-mode)\*
3. scan totp seed
4. confirm totp seed
5. Download recovery codes / confirm backup number / enroll in delegated recovery (one or more)

• User "prints recovery codes
• User copies recovery to clipboard and stores elsewhere
• User downloads a file containing the recovery codes

oreoshake

Keybase proof

I hereby claim:

• I am oreoshake on github.
• I am oreoshake (https://keybase.io/oreoshake) on keybase.
• I have a public key ASB-IgMwAQdkCZ0QKGX_YjWLn5ABKR5FPf26hoLA1KHOsgo

To claim this, I am signing this object:

oreoshake

#!/bin/bash

set -e

prevHEAD=$1
newHEAD=$2
checkoutType=$3

[[ $checkoutType == 1 ]] && checkoutType='branch' ||
                            checkoutType='file' ;

oreoshake

diff --git a/Dockerfile b/Dockerfile
index d63fcbe..22d87cd 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -11,21 +11,22 @@ ENV DISPLAY :99
 
 RUN rm -rf /root/bmp
 
-# use COPY for local testing, use the RUN command in CI
-COPY . /root/bmp

oreoshake

As of July 8, 2016 I will be resigning to become the new CEO of GitLob.

oreoshake

asdffffff

oreoshake

require 'octokit'
require 'parallel'

DEPENDENCY_FILES = %w(
  Gemfile
  Gemfile.lock
  package.json
  bower.json
  composer.json
  requirements.txt

oreoshake

#!/usr/bin/env shell-ruby
#/ Usage: gh-bounty-writeup hackerone_issue_id github_username [issues_repo] [writeup_repo]
#/

require "bounty"

raise("HACKERONE_TOKEN must be set") unless ENV["HACKERONE_TOKEN"]
raise("HACKERONE_TOKEN_NAME must be set") unless ENV["HACKERONE_TOKEN_NAME"]

usage = File.read(__FILE__).lines[1][3..-1]

oreoshake

[Neils-MacBook-Pro rails (master *>)]$ rbenv rehash
[Neils-MacBook-Pro rails (master *>)]$ which rails
/Users/neil/.rbenv/shims/rails
[Neils-MacBook-Pro rails (master *>)]$ which gem
/Users/neil/.rbenv/shims/gem
[Neils-MacBook-Pro rails (master *>)]$ rails -v
Rails 4.2.6
[Neils-MacBook-Pro rails (master *>)]$ gem uninstall rails

Select gem to uninstall:

oreoshake

• No inline script
• no eval
• no mixed content
• https required
• no referrer leaks
• no tabnabbing
• no cross origin framing
• no cross window/tab references
• no unpinned certs
• no non-Sri resources