Encrypted Credentials on Rails 5.2: Secrets to Success
summary
Rails 5.2 replaces encrypted secrets with Credentials that promise atomic deploys, no env var sprawl, and always-on encryption using Rails.application.credentials and the underlying EncryptedConfiguration API. Demo shows rails new, running rails credentials:edit, reading values via Rails.application.credentials.foo, and creating another file encrypted with a separate key file named master.key. Encryption reuses MessageEncryptor with AES-128-GCM. Historical notes include DES 56 bit weakness, 15 AES submissions and 5 finalists leading to Rijndael chosen in 2000.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:53Who is this for
- 2:15What are secrets
- 6:45How to use encrypted secrets
- 7:50Demo
- 15:21Using Encryption
- 20:48Encrypted Configuration
- 21:24AES
- 21:51Stream vs Block
- 22:37What is DES
- 23:39How DES works
- 27:01AES Standard
- 29:45Should you use credentialstrike
- 30:52Alternatives
related talks
38mActiveRecord::Encryption; Stop Hackers from...
36mModern Cryptography for the Absolute Beginner
40mA Better Way To Manage Secrets
31mRails Application Security in Practice
27mGo Auth Urself
29mData encryption made easy
38mKeeping Secrets - A Practical Approach to Managing Credentials
43mSecuring Your Site