bermannoah

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

bermannoah

1. rails new <project_name> -d postgresql --skip-turbolinks --skip-spring -T

• -d postgresql sets up the project to use PostgreSQL
• --skip-turbolinks & --skip-spring creates a project that does not use turbolinks or spring
• -T skips the creation of the test directory and use of Test::Unit

2. In the Gemfile:

• Available to all environments:
  • gem 'figaro' - store environment variables securely across your app (docs)
  • Uncomment gem 'bcrypt', '~> 3.1.7' if you will be hosting your own user accounts with passwords (docs)
• Inside of group :test:
  • gem 'rspec-rails' - user rspec in place of minitest (docs)

bermannoah

Turing School Prework - Noah Berman

Task A- Practice Typing:

• screenshots of scores are posted in comments

Task B- Algorithmic Thinking & Logic:

• screenshots of completed sections are posted in comments

Task C- Create your Gist: https://gist.github.com/ofmistakes/631d4583c9369cd2eb070efb90b168eb