closed-social
/
mastodon
3
0
Fork 2
Code Issues 5 Pull Requests 0 Projects 0 Releases 3 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2710 Commits
4 Branches
567 MiB
Tree: 2bd132d458
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '2bd132d458'
${ noResults }
mastodon/app/javascript/styles/lists.scss

20 lines
252 B
Raw Normal View History

Clean up stylesheet organization (#1591)
7 years ago
​
​
​
​
​
​
​
Add recovery code support for two-factor auth (#1773) * Add recovery code support for two-factor auth When users enable two-factor auth, the app now generates ten single-use recovery codes. Users are encouraged to print the codes and store them in a safe place. The two-factor prompt during login now accepts both OTP codes and recovery codes. The two-factor settings UI allows users to regenerated lost recovery codes. Users who have set up two-factor auth prior to this feature being added can use it to generate recovery codes for the first time. Fixes #563 and fixes #987 * Set OTP_SECRET in test enviroment * add missing .html to view file names
7 years ago
​
Fix up recovery codes design a little (#1866)
7 years ago
2FA controller cleanup (#2296) * Add spec coverage for settings/two_factor_auth area * extract setup method for qr code * Move otp required check to before action * Merge method only used once * Remove duplicate view * Consolidate creation of @codes for backup * Move settings/2fq#recovery_codes to settings/recovery_codes#create * Rename settings/two_factor_auth#disable to #destroy * Add coverage for the otp required path on 2fa#show * Clean up the recovery codes list styles * Move settings/two_factor_auth to settings/two_factor_authentication * Reorganize the settings two factor auth area Updated to use a flow like: - settings/two_factor_authentication goes to a #show view which has a button either enable or disable 2fa on the account - the disable button turns off the otp requirement for the user - the enable button cycles the user secret and redirects to a confirmation page - the confirmation page is a #new view which shows the QR code for user - that page posts to #create which verifies the code, and creates the recovery codes - that create action shares a view with a recovery codes controller which can be used separately to reset codes if needed
7 years ago
​
​
​
​
​
​
​
Add recovery code support for two-factor auth (#1773) * Add recovery code support for two-factor auth When users enable two-factor auth, the app now generates ten single-use recovery codes. Users are encouraged to print the codes and store them in a safe place. The two-factor prompt during login now accepts both OTP codes and recovery codes. The two-factor settings UI allows users to regenerated lost recovery codes. Users who have set up two-factor auth prior to this feature being added can use it to generate recovery codes for the first time. Fixes #563 and fixes #987 * Set OTP_SECRET in test enviroment * add missing .html to view file names
7 years ago
 
  1. .no-list {
  2.   list-style: none;
  3. 

  4.   li {
  5.     display: inline-block;
  6.     margin: 0 5px;
  7.   }
  8. }
  9. 

  10. .recovery-codes {
  11.   list-style: none;
  12.   margin: 0 auto;
  13.   text-align: center;
  14. 

  15.   li {
  16.     font-size: 125%;
  17.     line-height: 1.5;
  18.     letter-spacing: 1px;
  19.   }
  20. }