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.

844 lines
21 KiB

6 years ago
6 years ago
6 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
6 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
6 years ago
Version bumps for ruby and misc gems (#1159) * Update rspec-rails to version 3.5.2 * Update addressable to version 2.5.1 * Update autoprefixer-rails to version 6.7.7.1 * Update bullet to version 5.5.1 * Update domain_name to version 0.5.20170404 * Update letter_opener_web to version 1.3.1 * Upate redis-rails to version 5.0.2 * Update active_record_query_trace to version 1.5.4 * Update capistrano-rails to version 1.2.3 * Update dotenv-rails to version 2.2.0 * Update pg to version 0.20.0 * Update tilt to version 2.0.7 * Update warden to version 1.2.7 * Update tins to version 1.13.2 * Update terminal-table to version 1.7.3 * Update oj to version 2.18.5 * Update simplecov to version 0.14.1 * Update uglifier to version 3.1.13 * Update hashdiff to version 0.3.2 * Update webmock to version 2.3.2 * Update devise to version 4.2.1 * Use ruby version 2.4.1 * Update sass to version 3.4.23 * Update puma to version 3.8.2 * Update will_paginate to version 3.1.5 * Update font-awesome-rails to version 4.7.0.1 * Update fuubar to version 2.2.0 * Update pry-rails to version 0.3.6 * Update simple-navigation to version 4.0.5 * Update rubocop to version 0.48.1 * Update doorkeeper to version 4.2.5 * Update faker to version 1.7.3 * Update aws-sdk to version 2.9.5 * Update fabrication to version 2.16.1 * Update hamlit-rails to version 0.2.0 * Update http to version 2.2.1 * Update httplog to version 0.99.2 * Update sidekiq to version 4.2.10 * Update rspec-sidekiq to version 3.0.0 * Update pghero to version 1.6.4 * Update rack-cors to version 0.4.1 * Update i18n-tasks to version 0.9.13 * Update ruby-oembed to version 0.12.0 * Update jquery-rails to version 4.3.1 * Update simple_form to version 3.4.0 * Update react-rails to version 1.11.0 * Update aws-sdk to version 2.9.6 * Update sidekiq-unique-jobs to version 5.0.0 * Update uglifier to version 3.2.0
5 years ago
6 years ago
6 years ago
6 years ago
Web Push Notifications (#3243) * feat: Register push subscription * feat: Notify when mentioned * feat: Boost, favourite, reply, follow, follow request * feat: Notification interaction * feat: Handle change of public key * feat: Unsubscribe if things go wrong * feat: Do not send normal notifications if push is enabled * feat: Focus client if open * refactor: Move push logic to WebPushSubscription * feat: Better title and body * feat: Localize messages * chore: Fix lint errors * feat: Settings * refactor: Lazy load * fix: Check if push settings exist * feat: Device-based preferences * refactor: Simplify logic * refactor: Pull request feedback * refactor: Pull request feedback * refactor: Create /api/web/push_subscriptions endpoint * feat: Spec PushSubscriptionController * refactor: WebPushSubscription => Web::PushSubscription * feat: Spec Web::PushSubscription * feat: Display first media attachment * feat: Support direction * fix: Stuff broken while rebasing * refactor: Integration with session activations * refactor: Cleanup * refactor: Simplify implementation * feat: Set VAPID keys via environment * chore: Comments * fix: Crash when no alerts * fix: Set VAPID keys in testing environment * fix: Follow link * feat: Notification actions * fix: Delete previous subscription * chore: Temporary logs * refactor: Move migration to a later date * fix: Fetch the correct session activation and misc bugs * refactor: Move migration to a later date * fix: Remove follow request (no notifications) * feat: Send administrator contact to push service * feat: Set time-to-live * fix: Do not show sensitive images * fix: Reducer crash in error handling * feat: Add badge * chore: Fix lint error * fix: Checkbox label overlap * fix: Check for payload support * fix: Rename action "type" (crash in latest Chrome) * feat: Action to expand notification * fix: Lint errors * fix: Unescape notification body * fix: Do not allow boosting if the status is hidden * feat: Add VAPID keys to the production sample environment * fix: Strip HTML tags from status * refactor: Better error messages * refactor: Handle browser not implementing the VAPID protocol (Samsung Internet) * fix: Error when target_status is nil * fix: Handle lack of image * fix: Delete reference to invalid subscriptions * feat: Better error handling * fix: Unescape HTML characters after tags are striped * refactor: Simpify code * fix: Modify to work with #4091 * Sort strings alphabetically * i18n: Updated Polish translation it annoys me that it's not fully localized :P * refactor: Use current_session in PushSubscriptionController * fix: Rebase mistake * fix: Set cacheName to mastodon * refactor: Pull request feedback * refactor: Remove logging statements * chore(yarn): Fix conflicts with master * chore(yarn): Copy latest from master * chore(yarn): Readd offline-plugin * refactor: Use save! and update! * refactor: Send notifications async * fix: Allow retry when push fails * fix: Save track for failed pushes * fix: Minify sw.js * fix: Remove account_id from fabricator
4 years ago
6 years ago
6 years ago
6 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
Version bumps for ruby and misc gems (#1159) * Update rspec-rails to version 3.5.2 * Update addressable to version 2.5.1 * Update autoprefixer-rails to version 6.7.7.1 * Update bullet to version 5.5.1 * Update domain_name to version 0.5.20170404 * Update letter_opener_web to version 1.3.1 * Upate redis-rails to version 5.0.2 * Update active_record_query_trace to version 1.5.4 * Update capistrano-rails to version 1.2.3 * Update dotenv-rails to version 2.2.0 * Update pg to version 0.20.0 * Update tilt to version 2.0.7 * Update warden to version 1.2.7 * Update tins to version 1.13.2 * Update terminal-table to version 1.7.3 * Update oj to version 2.18.5 * Update simplecov to version 0.14.1 * Update uglifier to version 3.1.13 * Update hashdiff to version 0.3.2 * Update webmock to version 2.3.2 * Update devise to version 4.2.1 * Use ruby version 2.4.1 * Update sass to version 3.4.23 * Update puma to version 3.8.2 * Update will_paginate to version 3.1.5 * Update font-awesome-rails to version 4.7.0.1 * Update fuubar to version 2.2.0 * Update pry-rails to version 0.3.6 * Update simple-navigation to version 4.0.5 * Update rubocop to version 0.48.1 * Update doorkeeper to version 4.2.5 * Update faker to version 1.7.3 * Update aws-sdk to version 2.9.5 * Update fabrication to version 2.16.1 * Update hamlit-rails to version 0.2.0 * Update http to version 2.2.1 * Update httplog to version 0.99.2 * Update sidekiq to version 4.2.10 * Update rspec-sidekiq to version 3.0.0 * Update pghero to version 1.6.4 * Update rack-cors to version 0.4.1 * Update i18n-tasks to version 0.9.13 * Update ruby-oembed to version 0.12.0 * Update jquery-rails to version 4.3.1 * Update simple_form to version 3.4.0 * Update react-rails to version 1.11.0 * Update aws-sdk to version 2.9.6 * Update sidekiq-unique-jobs to version 5.0.0 * Update uglifier to version 3.2.0
5 years ago
6 years ago
6 years ago
Version bumps for ruby and misc gems (#1159) * Update rspec-rails to version 3.5.2 * Update addressable to version 2.5.1 * Update autoprefixer-rails to version 6.7.7.1 * Update bullet to version 5.5.1 * Update domain_name to version 0.5.20170404 * Update letter_opener_web to version 1.3.1 * Upate redis-rails to version 5.0.2 * Update active_record_query_trace to version 1.5.4 * Update capistrano-rails to version 1.2.3 * Update dotenv-rails to version 2.2.0 * Update pg to version 0.20.0 * Update tilt to version 2.0.7 * Update warden to version 1.2.7 * Update tins to version 1.13.2 * Update terminal-table to version 1.7.3 * Update oj to version 2.18.5 * Update simplecov to version 0.14.1 * Update uglifier to version 3.1.13 * Update hashdiff to version 0.3.2 * Update webmock to version 2.3.2 * Update devise to version 4.2.1 * Use ruby version 2.4.1 * Update sass to version 3.4.23 * Update puma to version 3.8.2 * Update will_paginate to version 3.1.5 * Update font-awesome-rails to version 4.7.0.1 * Update fuubar to version 2.2.0 * Update pry-rails to version 0.3.6 * Update simple-navigation to version 4.0.5 * Update rubocop to version 0.48.1 * Update doorkeeper to version 4.2.5 * Update faker to version 1.7.3 * Update aws-sdk to version 2.9.5 * Update fabrication to version 2.16.1 * Update hamlit-rails to version 0.2.0 * Update http to version 2.2.1 * Update httplog to version 0.99.2 * Update sidekiq to version 4.2.10 * Update rspec-sidekiq to version 3.0.0 * Update pghero to version 1.6.4 * Update rack-cors to version 0.4.1 * Update i18n-tasks to version 0.9.13 * Update ruby-oembed to version 0.12.0 * Update jquery-rails to version 4.3.1 * Update simple_form to version 3.4.0 * Update react-rails to version 1.11.0 * Update aws-sdk to version 2.9.6 * Update sidekiq-unique-jobs to version 5.0.0 * Update uglifier to version 3.2.0
5 years ago
6 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
6 years ago
6 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
6 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
Web Push Notifications (#3243) * feat: Register push subscription * feat: Notify when mentioned * feat: Boost, favourite, reply, follow, follow request * feat: Notification interaction * feat: Handle change of public key * feat: Unsubscribe if things go wrong * feat: Do not send normal notifications if push is enabled * feat: Focus client if open * refactor: Move push logic to WebPushSubscription * feat: Better title and body * feat: Localize messages * chore: Fix lint errors * feat: Settings * refactor: Lazy load * fix: Check if push settings exist * feat: Device-based preferences * refactor: Simplify logic * refactor: Pull request feedback * refactor: Pull request feedback * refactor: Create /api/web/push_subscriptions endpoint * feat: Spec PushSubscriptionController * refactor: WebPushSubscription => Web::PushSubscription * feat: Spec Web::PushSubscription * feat: Display first media attachment * feat: Support direction * fix: Stuff broken while rebasing * refactor: Integration with session activations * refactor: Cleanup * refactor: Simplify implementation * feat: Set VAPID keys via environment * chore: Comments * fix: Crash when no alerts * fix: Set VAPID keys in testing environment * fix: Follow link * feat: Notification actions * fix: Delete previous subscription * chore: Temporary logs * refactor: Move migration to a later date * fix: Fetch the correct session activation and misc bugs * refactor: Move migration to a later date * fix: Remove follow request (no notifications) * feat: Send administrator contact to push service * feat: Set time-to-live * fix: Do not show sensitive images * fix: Reducer crash in error handling * feat: Add badge * chore: Fix lint error * fix: Checkbox label overlap * fix: Check for payload support * fix: Rename action "type" (crash in latest Chrome) * feat: Action to expand notification * fix: Lint errors * fix: Unescape notification body * fix: Do not allow boosting if the status is hidden * feat: Add VAPID keys to the production sample environment * fix: Strip HTML tags from status * refactor: Better error messages * refactor: Handle browser not implementing the VAPID protocol (Samsung Internet) * fix: Error when target_status is nil * fix: Handle lack of image * fix: Delete reference to invalid subscriptions * feat: Better error handling * fix: Unescape HTML characters after tags are striped * refactor: Simpify code * fix: Modify to work with #4091 * Sort strings alphabetically * i18n: Updated Polish translation it annoys me that it's not fully localized :P * refactor: Use current_session in PushSubscriptionController * fix: Rebase mistake * fix: Set cacheName to mastodon * refactor: Pull request feedback * refactor: Remove logging statements * chore(yarn): Fix conflicts with master * chore(yarn): Copy latest from master * chore(yarn): Readd offline-plugin * refactor: Use save! and update! * refactor: Send notifications async * fix: Allow retry when push fails * fix: Save track for failed pushes * fix: Minify sw.js * fix: Remove account_id from fabricator
4 years ago
Add follower synchronization mechanism (#14510) * Add support for followers synchronization on the receiving end Check the `collectionSynchronization` attribute on `Create` and `Announce` activities and synchronize followers from provided collection if possible. * Add tests for followers synchronization on the receiving end * Add support for follower synchronization on the sender's end * Add tests for the sending end * Switch from AS attributes to HTTP header Replace the custom `collectionSynchronization` ActivityStreams attribute by an HTTP header (`X-AS-Collection-Synchronization`) with the same syntax as the `Signature` header and the following fields: - `collectionId` to specify which collection to synchronize - `digest` for the SHA256 hex-digest of the list of followers known on the receiving instance (where “receiving instance” is determined by accounts sharing the same host name for their ActivityPub actor `id`) - `url` of a collection that should be fetched by the instance actor Internally, move away from the webfinger-based `domain` attribute and use account `uri` prefix to group accounts. * Add environment variable to disable followers synchronization Since the whole mechanism relies on some new preconditions that, in some extremely rare cases, might not be met, add an environment variable (DISABLE_FOLLOWERS_SYNCHRONIZATION) to disable the mechanism altogether and avoid followers being incorrectly removed. The current conditions are: 1. all managed accounts' actor `id` and inbox URL have the same URI scheme and netloc. 2. all accounts whose actor `id` or inbox URL share the same URI scheme and netloc as a managed account must be managed by the same Mastodon instance as well. As far as Mastodon is concerned, breaking those preconditions require extensive configuration changes in the reverse proxy and might also cause other issues. Therefore, this environment variable provides a way out for people with highly unusual configurations, and can be safely ignored for the overwhelming majority of Mastodon administrators. * Only set follower synchronization header on non-public statuses This is to avoid unnecessary computations and allow Follow-related activities to be handled by the usual codepath instead of going through the synchronization mechanism (otherwise, any Follow/Undo/Accept activity would trigger the synchronization mechanism even if processing the activity itself would be enough to re-introduce synchronization) * Change how ActivityPub::SynchronizeFollowersService handles follow requests If the remote lists a local follower which we only know has sent a follow request, consider the follow request as accepted instead of sending an Undo. * Integrate review feeback - rename X-AS-Collection-Synchronization to Collection-Synchronization - various minor refactoring and code style changes * Only select required fields when computing followers_hash * Use actor URI rather than webfinger domain in synchronization endpoint * Change hash computation to be a XOR of individual hashes Makes it much easier to be memory-efficient, and avoid sorting discrepancy issues. * Marginally improve followers_hash computation speed * Further improve hash computation performances by using pluck_each
1 year ago
6 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
1 year ago
Web Push Notifications (#3243) * feat: Register push subscription * feat: Notify when mentioned * feat: Boost, favourite, reply, follow, follow request * feat: Notification interaction * feat: Handle change of public key * feat: Unsubscribe if things go wrong * feat: Do not send normal notifications if push is enabled * feat: Focus client if open * refactor: Move push logic to WebPushSubscription * feat: Better title and body * feat: Localize messages * chore: Fix lint errors * feat: Settings * refactor: Lazy load * fix: Check if push settings exist * feat: Device-based preferences * refactor: Simplify logic * refactor: Pull request feedback * refactor: Pull request feedback * refactor: Create /api/web/push_subscriptions endpoint * feat: Spec PushSubscriptionController * refactor: WebPushSubscription => Web::PushSubscription * feat: Spec Web::PushSubscription * feat: Display first media attachment * feat: Support direction * fix: Stuff broken while rebasing * refactor: Integration with session activations * refactor: Cleanup * refactor: Simplify implementation * feat: Set VAPID keys via environment * chore: Comments * fix: Crash when no alerts * fix: Set VAPID keys in testing environment * fix: Follow link * feat: Notification actions * fix: Delete previous subscription * chore: Temporary logs * refactor: Move migration to a later date * fix: Fetch the correct session activation and misc bugs * refactor: Move migration to a later date * fix: Remove follow request (no notifications) * feat: Send administrator contact to push service * feat: Set time-to-live * fix: Do not show sensitive images * fix: Reducer crash in error handling * feat: Add badge * chore: Fix lint error * fix: Checkbox label overlap * fix: Check for payload support * fix: Rename action "type" (crash in latest Chrome) * feat: Action to expand notification * fix: Lint errors * fix: Unescape notification body * fix: Do not allow boosting if the status is hidden * feat: Add VAPID keys to the production sample environment * fix: Strip HTML tags from status * refactor: Better error messages * refactor: Handle browser not implementing the VAPID protocol (Samsung Internet) * fix: Error when target_status is nil * fix: Handle lack of image * fix: Delete reference to invalid subscriptions * feat: Better error handling * fix: Unescape HTML characters after tags are striped * refactor: Simpify code * fix: Modify to work with #4091 * Sort strings alphabetically * i18n: Updated Polish translation it annoys me that it's not fully localized :P * refactor: Use current_session in PushSubscriptionController * fix: Rebase mistake * fix: Set cacheName to mastodon * refactor: Pull request feedback * refactor: Remove logging statements * chore(yarn): Fix conflicts with master * chore(yarn): Copy latest from master * chore(yarn): Readd offline-plugin * refactor: Use save! and update! * refactor: Send notifications async * fix: Allow retry when push fails * fix: Save track for failed pushes * fix: Minify sw.js * fix: Remove account_id from fabricator
4 years ago
Add follower synchronization mechanism (#14510) * Add support for followers synchronization on the receiving end Check the `collectionSynchronization` attribute on `Create` and `Announce` activities and synchronize followers from provided collection if possible. * Add tests for followers synchronization on the receiving end * Add support for follower synchronization on the sender's end * Add tests for the sending end * Switch from AS attributes to HTTP header Replace the custom `collectionSynchronization` ActivityStreams attribute by an HTTP header (`X-AS-Collection-Synchronization`) with the same syntax as the `Signature` header and the following fields: - `collectionId` to specify which collection to synchronize - `digest` for the SHA256 hex-digest of the list of followers known on the receiving instance (where “receiving instance” is determined by accounts sharing the same host name for their ActivityPub actor `id`) - `url` of a collection that should be fetched by the instance actor Internally, move away from the webfinger-based `domain` attribute and use account `uri` prefix to group accounts. * Add environment variable to disable followers synchronization Since the whole mechanism relies on some new preconditions that, in some extremely rare cases, might not be met, add an environment variable (DISABLE_FOLLOWERS_SYNCHRONIZATION) to disable the mechanism altogether and avoid followers being incorrectly removed. The current conditions are: 1. all managed accounts' actor `id` and inbox URL have the same URI scheme and netloc. 2. all accounts whose actor `id` or inbox URL share the same URI scheme and netloc as a managed account must be managed by the same Mastodon instance as well. As far as Mastodon is concerned, breaking those preconditions require extensive configuration changes in the reverse proxy and might also cause other issues. Therefore, this environment variable provides a way out for people with highly unusual configurations, and can be safely ignored for the overwhelming majority of Mastodon administrators. * Only set follower synchronization header on non-public statuses This is to avoid unnecessary computations and allow Follow-related activities to be handled by the usual codepath instead of going through the synchronization mechanism (otherwise, any Follow/Undo/Accept activity would trigger the synchronization mechanism even if processing the activity itself would be enough to re-introduce synchronization) * Change how ActivityPub::SynchronizeFollowersService handles follow requests If the remote lists a local follower which we only know has sent a follow request, consider the follow request as accepted instead of sending an Undo. * Integrate review feeback - rename X-AS-Collection-Synchronization to Collection-Synchronization - various minor refactoring and code style changes * Only select required fields when computing followers_hash * Use actor URI rather than webfinger domain in synchronization endpoint * Change hash computation to be a XOR of individual hashes Makes it much easier to be memory-efficient, and avoid sorting discrepancy issues. * Marginally improve followers_hash computation speed * Further improve hash computation performances by using pluck_each
1 year ago
  1. GIT
  2. remote: https://github.com/ClearlyClaire/devise-two-factor
  3. revision: 594bb8a32e6f94df7e5ba7c9399eaf9ff25bac0d
  4. ref: 594bb8a32e6f94df7e5ba7c9399eaf9ff25bac0d
  5. specs:
  6. devise-two-factor (3.1.0)
  7. activesupport (< 7.0)
  8. attr_encrypted (>= 1.3, < 4, != 2)
  9. devise
  10. railties (< 7.0)
  11. rotp (~> 6)
  12. GIT
  13. remote: https://github.com/Gargron/nsa
  14. revision: d1079e0cdafdfed7f9f35478d13b9bdaa65965c0
  15. ref: d1079e0cdafdfed7f9f35478d13b9bdaa65965c0
  16. specs:
  17. nsa (0.2.8)
  18. activesupport (>= 4.2, < 7)
  19. concurrent-ruby (~> 1.0, >= 1.0.2)
  20. sidekiq (>= 3.5)
  21. statsd-ruby (~> 1.4, >= 1.4.0)
  22. GIT
  23. remote: https://github.com/ianheggie/health_check
  24. revision: 0b799ead604f900ed50685e9b2d469cd2befba5b
  25. ref: 0b799ead604f900ed50685e9b2d469cd2befba5b
  26. specs:
  27. health_check (4.0.0.pre)
  28. rails (>= 4.0)
  29. GIT
  30. remote: https://github.com/nsommer/pluck_each
  31. revision: 73be0947c52fc54bf6d7085378db008358aac5eb
  32. ref: 73be0947c52fc54bf6d7085378db008358aac5eb
  33. specs:
  34. pluck_each (0.1.3)
  35. activerecord (>= 6.1.0)
  36. activesupport (>= 6.1.0)
  37. GIT
  38. remote: https://github.com/witgo/nilsimsa
  39. revision: fd184883048b922b176939f851338d0a4971a532
  40. ref: fd184883048b922b176939f851338d0a4971a532
  41. specs:
  42. nilsimsa (1.1.2)
  43. GEM
  44. remote: https://rubygems.org/
  45. specs:
  46. actioncable (6.1.3)
  47. actionpack (= 6.1.3)
  48. activesupport (= 6.1.3)
  49. nio4r (~> 2.0)
  50. websocket-driver (>= 0.6.1)
  51. actionmailbox (6.1.3)
  52. actionpack (= 6.1.3)
  53. activejob (= 6.1.3)
  54. activerecord (= 6.1.3)
  55. activestorage (= 6.1.3)
  56. activesupport (= 6.1.3)
  57. mail (>= 2.7.1)
  58. actionmailer (6.1.3)
  59. actionpack (= 6.1.3)
  60. actionview (= 6.1.3)
  61. activejob (= 6.1.3)
  62. activesupport (= 6.1.3)
  63. mail (~> 2.5, >= 2.5.4)
  64. rails-dom-testing (~> 2.0)
  65. actionpack (6.1.3)
  66. actionview (= 6.1.3)
  67. activesupport (= 6.1.3)
  68. rack (~> 2.0, >= 2.0.9)
  69. rack-test (>= 0.6.3)
  70. rails-dom-testing (~> 2.0)
  71. rails-html-sanitizer (~> 1.0, >= 1.2.0)
  72. actiontext (6.1.3)
  73. actionpack (= 6.1.3)
  74. activerecord (= 6.1.3)
  75. activestorage (= 6.1.3)
  76. activesupport (= 6.1.3)
  77. nokogiri (>= 1.8.5)
  78. actionview (6.1.3)
  79. activesupport (= 6.1.3)
  80. builder (~> 3.1)
  81. erubi (~> 1.4)
  82. rails-dom-testing (~> 2.0)
  83. rails-html-sanitizer (~> 1.1, >= 1.2.0)
  84. active_model_serializers (0.10.12)
  85. actionpack (>= 4.1, < 6.2)
  86. activemodel (>= 4.1, < 6.2)
  87. case_transform (>= 0.2)
  88. jsonapi-renderer (>= 0.1.1.beta1, < 0.3)
  89. active_record_query_trace (1.8)
  90. activejob (6.1.3)
  91. activesupport (= 6.1.3)
  92. globalid (>= 0.3.6)
  93. activemodel (6.1.3)
  94. activesupport (= 6.1.3)
  95. activerecord (6.1.3)
  96. activemodel (= 6.1.3)
  97. activesupport (= 6.1.3)
  98. activestorage (6.1.3)
  99. actionpack (= 6.1.3)
  100. activejob (= 6.1.3)
  101. activerecord (= 6.1.3)
  102. activesupport (= 6.1.3)
  103. marcel (~> 0.3.1)
  104. mimemagic (~> 0.3.2)
  105. activesupport (6.1.3)
  106. concurrent-ruby (~> 1.0, >= 1.0.2)
  107. i18n (>= 1.6, < 2)
  108. minitest (>= 5.1)
  109. tzinfo (~> 2.0)
  110. zeitwerk (~> 2.3)
  111. addressable (2.7.0)
  112. public_suffix (>= 2.0.2, < 5.0)
  113. airbrussh (1.4.0)
  114. sshkit (>= 1.6.1, != 1.7.0)
  115. android_key_attestation (0.3.0)
  116. annotate (3.1.1)
  117. activerecord (>= 3.2, < 7.0)
  118. rake (>= 10.4, < 14.0)
  119. ast (2.4.2)
  120. attr_encrypted (3.1.0)
  121. encryptor (~> 3.0.0)
  122. av (0.9.0)
  123. cocaine (~> 0.5.3)
  124. awrence (1.1.1)
  125. aws-eventstream (1.1.1)
  126. aws-partitions (1.434.0)
  127. aws-sdk-core (3.113.0)
  128. aws-eventstream (~> 1, >= 1.0.2)
  129. aws-partitions (~> 1, >= 1.239.0)
  130. aws-sigv4 (~> 1.1)
  131. jmespath (~> 1.0)
  132. aws-sdk-kms (1.43.0)
  133. aws-sdk-core (~> 3, >= 3.112.0)
  134. aws-sigv4 (~> 1.1)
  135. aws-sdk-s3 (1.92.0)
  136. aws-sdk-core (~> 3, >= 3.112.0)
  137. aws-sdk-kms (~> 1)
  138. aws-sigv4 (~> 1.1)
  139. aws-sigv4 (1.2.3)
  140. aws-eventstream (~> 1, >= 1.0.2)
  141. bcrypt (3.1.16)
  142. better_errors (2.9.1)
  143. coderay (>= 1.0.0)
  144. erubi (>= 1.0.0)
  145. rack (>= 0.9.0)
  146. bindata (2.4.8)
  147. binding_of_caller (1.0.0)
  148. debug_inspector (>= 0.0.1)
  149. blurhash (0.1.5)
  150. ffi (~> 1.14)
  151. bootsnap (1.6.0)
  152. msgpack (~> 1.0)
  153. brakeman (4.10.1)
  154. browser (4.2.0)
  155. brpoplpush-redis_script (0.1.2)
  156. concurrent-ruby (~> 1.0, >= 1.0.5)
  157. redis (>= 1.0, <= 5.0)
  158. builder (3.2.4)
  159. bullet (6.1.4)
  160. activesupport (>= 3.0.0)
  161. uniform_notifier (~> 1.11)
  162. bundler-audit (0.8.0)
  163. bundler (>= 1.2.0, < 3)
  164. thor (~> 1.0)
  165. byebug (11.1.3)
  166. capistrano (3.16.0)
  167. airbrussh (>= 1.0.0)
  168. i18n
  169. rake (>= 10.0.0)
  170. sshkit (>= 1.9.0)
  171. capistrano-bundler (2.0.1)
  172. capistrano (~> 3.1)
  173. capistrano-rails (1.6.1)
  174. capistrano (~> 3.1)
  175. capistrano-bundler (>= 1.1, < 3)
  176. capistrano-rbenv (2.2.0)
  177. capistrano (~> 3.1)
  178. sshkit (~> 1.3)
  179. capistrano-yarn (2.0.2)
  180. capistrano (~> 3.0)
  181. capybara (3.35.3)
  182. addressable
  183. mini_mime (>= 0.1.3)
  184. nokogiri (~> 1.8)
  185. rack (>= 1.6.0)
  186. rack-test (>= 0.6.3)
  187. regexp_parser (>= 1.5, < 3.0)
  188. xpath (~> 3.2)
  189. case_transform (0.2)
  190. activesupport
  191. cbor (0.5.9.6)
  192. charlock_holmes (0.7.7)
  193. chewy (5.2.0)
  194. activesupport (>= 5.2)
  195. elasticsearch (>= 2.0.0)
  196. elasticsearch-dsl
  197. chunky_png (1.3.15)
  198. cld3 (3.4.1)
  199. ffi (>= 1.1.0, < 1.15.0)
  200. climate_control (0.2.0)
  201. cocaine (0.5.8)
  202. climate_control (>= 0.0.3, < 1.0)
  203. coderay (1.1.3)
  204. color_diff (0.1)
  205. concurrent-ruby (1.1.8)
  206. connection_pool (2.2.3)
  207. cose (1.0.0)
  208. cbor (~> 0.5.9)
  209. openssl-signature_algorithm (~> 0.4.0)
  210. crack (0.4.5)
  211. rexml
  212. crass (1.0.6)
  213. css_parser (1.7.1)
  214. addressable
  215. debug_inspector (1.0.0)
  216. devise (4.7.3)
  217. bcrypt (~> 3.0)
  218. orm_adapter (~> 0.1)
  219. railties (>= 4.1.0)
  220. responders
  221. warden (~> 1.2.3)
  222. devise_pam_authenticatable2 (9.2.0)
  223. devise (>= 4.0.0)
  224. rpam2 (~> 4.0)
  225. diff-lcs (1.4.4)
  226. discard (1.2.0)
  227. activerecord (>= 4.2, < 7)
  228. docile (1.3.4)
  229. domain_name (0.5.20190701)
  230. unf (>= 0.0.5, < 1.0.0)
  231. doorkeeper (5.5.0)
  232. railties (>= 5)
  233. dotenv (2.7.6)
  234. dotenv-rails (2.7.6)
  235. dotenv (= 2.7.6)
  236. railties (>= 3.2)
  237. e2mmap (0.1.0)
  238. ed25519 (1.2.4)
  239. elasticsearch (7.10.1)
  240. elasticsearch-api (= 7.10.1)
  241. elasticsearch-transport (= 7.10.1)
  242. elasticsearch-api (7.10.1)
  243. multi_json
  244. elasticsearch-dsl (0.1.9)
  245. elasticsearch-transport (7.10.1)
  246. faraday (~> 1)
  247. multi_json
  248. encryptor (3.0.0)
  249. erubi (1.10.0)
  250. et-orbi (1.2.4)
  251. tzinfo
  252. excon (0.76.0)
  253. fabrication (2.21.1)
  254. faker (2.17.0)
  255. i18n (>= 1.6, < 2)
  256. faraday (1.3.0)
  257. faraday-net_http (~> 1.0)
  258. multipart-post (>= 1.2, < 3)
  259. ruby2_keywords
  260. faraday-net_http (1.0.1)
  261. fast_blank (1.0.0)
  262. fastimage (2.2.3)
  263. ffi (1.14.2)
  264. ffi-compiler (1.0.1)
  265. ffi (>= 1.0.0)
  266. rake
  267. fog-core (2.1.0)
  268. builder
  269. excon (~> 0.58)
  270. formatador (~> 0.2)
  271. mime-types
  272. fog-json (1.2.0)
  273. fog-core
  274. multi_json (~> 1.10)
  275. fog-openstack (0.3.10)
  276. fog-core (>= 1.45, <= 2.1.0)
  277. fog-json (>= 1.0)
  278. ipaddress (>= 0.8)
  279. formatador (0.2.5)
  280. fugit (1.3.9)
  281. et-orbi (~> 1.1, >= 1.1.8)
  282. raabro (~> 1.3)
  283. fuubar (2.5.1)
  284. rspec-core (~> 3.0)
  285. ruby-progressbar (~> 1.4)
  286. globalid (0.4.2)
  287. activesupport (>= 4.2.0)
  288. hamlit (2.13.0)
  289. temple (>= 0.8.2)
  290. thor
  291. tilt
  292. hamlit-rails (0.2.3)
  293. actionpack (>= 4.0.1)
  294. activesupport (>= 4.0.1)
  295. hamlit (>= 1.2.0)
  296. railties (>= 4.0.1)
  297. hamster (3.0.0)
  298. concurrent-ruby (~> 1.0)
  299. hashdiff (1.0.1)
  300. hashie (4.1.0)
  301. highline (2.0.3)
  302. hiredis (0.6.3)
  303. hkdf (0.3.0)
  304. htmlentities (4.3.4)
  305. http (4.4.1)
  306. addressable (~> 2.3)
  307. http-cookie (~> 1.0)
  308. http-form_data (~> 2.2)
  309. http-parser (~> 1.2.0)
  310. http-cookie (1.0.3)
  311. domain_name (~> 0.5)
  312. http-form_data (2.3.0)
  313. http-parser (1.2.1)
  314. ffi-compiler (>= 1.0, < 2.0)
  315. http_accept_language (2.1.1)
  316. httplog (1.4.3)
  317. rack (>= 1.0)
  318. rainbow (>= 2.0.0)
  319. i18n (1.8.9)
  320. concurrent-ruby (~> 1.0)
  321. i18n-tasks (0.9.34)
  322. activesupport (>= 4.0.2)
  323. ast (>= 2.1.0)
  324. erubi
  325. highline (>= 2.0.0)
  326. i18n
  327. parser (>= 2.2.3.0)
  328. rails-i18n
  329. rainbow (>= 2.2.2, < 4.0)
  330. terminal-table (>= 1.5.1)
  331. idn-ruby (0.1.0)
  332. ipaddress (0.8.3)
  333. iso-639 (0.3.5)
  334. jmespath (1.4.0)
  335. json (2.3.1)
  336. json-canonicalization (0.2.1)
  337. json-ld (3.1.9)
  338. htmlentities (~> 4.3)
  339. json-canonicalization (~> 0.2)
  340. link_header (~> 0.0, >= 0.0.8)
  341. multi_json (~> 1.14)
  342. rack (~> 2.0)
  343. rdf (~> 3.1)
  344. json-ld-preloaded (3.1.5)
  345. json-ld (~> 3.1)
  346. rdf (~> 3.1)
  347. jsonapi-renderer (0.2.2)
  348. jwt (2.2.2)
  349. kaminari (1.2.1)
  350. activesupport (>= 4.1.0)
  351. kaminari-actionview (= 1.2.1)
  352. kaminari-activerecord (= 1.2.1)
  353. kaminari-core (= 1.2.1)
  354. kaminari-actionview (1.2.1)
  355. actionview
  356. kaminari-core (= 1.2.1)
  357. kaminari-activerecord (1.2.1)
  358. activerecord
  359. kaminari-core (= 1.2.1)
  360. kaminari-core (1.2.1)
  361. launchy (2.5.0)
  362. addressable (~> 2.7)
  363. letter_opener (1.7.0)
  364. launchy (~> 2.2)
  365. letter_opener_web (1.4.0)
  366. actionmailer (>= 3.2)
  367. letter_opener (~> 1.0)
  368. railties (>= 3.2)
  369. link_header (0.0.8)
  370. lograge (0.11.2)
  371. actionpack (>= 4)
  372. activesupport (>= 4)
  373. railties (>= 4)
  374. request_store (~> 1.0)
  375. loofah (2.9.0)
  376. crass (~> 1.0.2)
  377. nokogiri (>= 1.5.9)
  378. mail (2.7.1)
  379. mini_mime (>= 0.1.1)
  380. makara (0.5.0)
  381. activerecord (>= 3.0.0)
  382. marcel (0.3.3)
  383. mimemagic (~> 0.3.2)
  384. mario-redis-lock (1.2.1)
  385. redis (>= 3.0.5)
  386. memory_profiler (1.0.0)
  387. method_source (1.0.0)
  388. microformats (4.2.1)
  389. json (~> 2.2)
  390. nokogiri (~> 1.10)
  391. mime-types (3.3.1)
  392. mime-types-data (~> 3.2015)
  393. mime-types-data (3.2020.0512)
  394. mimemagic (0.3.5)
  395. mini_mime (1.0.2)
  396. mini_portile2 (2.5.0)
  397. minitest (5.14.4)
  398. msgpack (1.4.2)
  399. multi_json (1.15.0)
  400. multipart-post (2.1.1)
  401. net-ldap (0.17.0)
  402. net-scp (3.0.0)
  403. net-ssh (>= 2.6.5, < 7.0.0)
  404. net-ssh (6.1.0)
  405. nio4r (2.5.7)
  406. nokogiri (1.11.2)
  407. mini_portile2 (~> 2.5.0)
  408. racc (~> 1.4)
  409. nokogumbo (2.0.4)
  410. nokogiri (~> 1.8, >= 1.8.4)
  411. oj (3.11.3)
  412. omniauth (1.9.1)
  413. hashie (>= 3.4.6)
  414. rack (>= 1.6.2, < 3)
  415. omniauth-cas (2.0.0)
  416. addressable (~> 2.3)
  417. nokogiri (~> 1.5)
  418. omniauth (~> 1.2)
  419. omniauth-rails_csrf_protection (0.1.2)
  420. actionpack (>= 4.2)
  421. omniauth (>= 1.3.1)
  422. omniauth-saml (1.10.3)
  423. omniauth (~> 1.3, >= 1.3.2)
  424. ruby-saml (~> 1.9)
  425. openssl (2.2.0)
  426. openssl-signature_algorithm (0.4.0)
  427. orm_adapter (0.5.0)
  428. ox (2.14.4)
  429. paperclip (6.0.0)
  430. activemodel (>= 4.2.0)
  431. activesupport (>= 4.2.0)
  432. mime-types
  433. mimemagic (~> 0.3.0)
  434. terrapin (~> 0.6.0)
  435. paperclip-av-transcoder (0.6.4)
  436. av (~> 0.9.0)
  437. paperclip (>= 2.5.2)
  438. parallel (1.20.1)
  439. parallel_tests (3.5.2)
  440. parallel
  441. parser (3.0.0.0)
  442. ast (~> 2.4.1)
  443. parslet (2.0.0)
  444. pastel (0.8.0)
  445. tty-color (~> 0.5)
  446. pg (1.2.3)
  447. pghero (2.8.0)
  448. activerecord (>= 5)
  449. pkg-config (1.4.5)
  450. posix-spawn (0.3.15)
  451. premailer (1.14.2)
  452. addressable
  453. css_parser (>= 1.6.0)
  454. htmlentities (>= 4.0.0)
  455. premailer-rails (1.11.1)
  456. actionmailer (>= 3)
  457. premailer (~> 1.7, >= 1.7.9)
  458. private_address_check (0.5.0)
  459. pry (0.13.1)
  460. coderay (~> 1.1)
  461. method_source (~> 1.0)
  462. pry-byebug (3.9.0)
  463. byebug (~> 11.0)
  464. pry (~> 0.13.0)
  465. pry-rails (0.3.9)
  466. pry (>= 0.10.4)
  467. public_suffix (4.0.6)
  468. puma (5.2.2)
  469. nio4r (~> 2.0)
  470. pundit (2.1.0)
  471. activesupport (>= 3.0.0)
  472. raabro (1.3.3)
  473. racc (1.5.2)
  474. rack (2.2.3)
  475. rack-attack (6.5.0)
  476. rack (>= 1.0, < 3)
  477. rack-cors (1.1.1)
  478. rack (>= 2.0.0)
  479. rack-proxy (0.6.5)
  480. rack
  481. rack-test (1.1.0)
  482. rack (>= 1.0, < 3)
  483. rails (6.1.3)
  484. actioncable (= 6.1.3)
  485. actionmailbox (= 6.1.3)
  486. actionmailer (= 6.1.3)
  487. actionpack (= 6.1.3)
  488. actiontext (= 6.1.3)
  489. actionview (= 6.1.3)
  490. activejob (= 6.1.3)
  491. activemodel (= 6.1.3)
  492. activerecord (= 6.1.3)
  493. activestorage (= 6.1.3)
  494. activesupport (= 6.1.3)
  495. bundler (>= 1.15.0)
  496. railties (= 6.1.3)
  497. sprockets-rails (>= 2.0.0)
  498. rails-controller-testing (1.0.5)
  499. actionpack (>= 5.0.1.rc1)
  500. actionview (>= 5.0.1.rc1)
  501. activesupport (>= 5.0.1.rc1)
  502. rails-dom-testing (2.0.3)
  503. activesupport (>= 4.2.0)
  504. nokogiri (>= 1.6)
  505. rails-html-sanitizer (1.3.0)
  506. loofah (~> 2.3)
  507. rails-i18n (6.0.0)
  508. i18n (>= 0.7, < 2)
  509. railties (>= 6.0.0, < 7)
  510. rails-settings-cached (0.6.6)
  511. rails (>= 4.2.0)
  512. railties (6.1.3)
  513. actionpack (= 6.1.3)
  514. activesupport (= 6.1.3)
  515. method_source
  516. rake (>= 0.8.7)
  517. thor (~> 1.0)
  518. rainbow (3.0.0)
  519. rake (13.0.3)
  520. rdf (3.1.13)
  521. hamster (~> 3.0)
  522. link_header (~> 0.0, >= 0.0.8)
  523. rdf-normalize (0.4.0)
  524. rdf (~> 3.1)
  525. redis (4.2.5)
  526. redis-namespace (1.8.1)
  527. redis (>= 3.0.4)
  528. regexp_parser (2.1.1)
  529. request_store (1.5.0)
  530. rack (>= 1.4)
  531. responders (3.0.1)
  532. actionpack (>= 5.0)
  533. railties (>= 5.0)
  534. rexml (3.2.4)
  535. rotp (6.2.0)
  536. rpam2 (4.0.2)
  537. rqrcode (1.2.0)
  538. chunky_png (~> 1.0)
  539. rqrcode_core (~> 0.2)
  540. rqrcode_core (0.2.0)
  541. rspec-core (3.10.1)
  542. rspec-support (~> 3.10.0)
  543. rspec-expectations (3.10.1)
  544. diff-lcs (>= 1.2.0, < 2.0)
  545. rspec-support (~> 3.10.0)
  546. rspec-mocks (3.10.2)
  547. diff-lcs (>= 1.2.0, < 2.0)
  548. rspec-support (~> 3.10.0)
  549. rspec-rails (5.0.1)
  550. actionpack (>= 5.2)
  551. activesupport (>= 5.2)
  552. railties (>= 5.2)
  553. rspec-core (~> 3.10)
  554. rspec-expectations (~> 3.10)
  555. rspec-mocks (~> 3.10)
  556. rspec-support (~> 3.10)
  557. rspec-sidekiq (3.1.0)
  558. rspec-core (~> 3.0, >= 3.0.0)
  559. sidekiq (>= 2.4.0)
  560. rspec-support (3.10.2)
  561. rspec_junit_formatter (0.4.1)
  562. rspec-core (>= 2, < 4, != 2.12.0)
  563. rubocop (1.11.0)
  564. parallel (~> 1.10)
  565. parser (>= 3.0.0.0)
  566. rainbow (>= 2.2.2, < 4.0)
  567. regexp_parser (>= 1.8, < 3.0)
  568. rexml
  569. rubocop-ast (>= 1.2.0, < 2.0)
  570. ruby-progressbar (~> 1.7)
  571. unicode-display_width (>= 1.4.0, < 3.0)
  572. rubocop-ast (1.4.1)
  573. parser (>= 2.7.1.5)
  574. rubocop-rails (2.9.1)
  575. activesupport (>= 4.2.0)
  576. rack (>= 1.1)
  577. rubocop (>= 0.90.0, < 2.0)
  578. ruby-progressbar (1.11.0)
  579. ruby-saml (1.11.0)
  580. nokogiri (>= 1.5.10)
  581. ruby2_keywords (0.0.4)
  582. rufus-scheduler (3.6.0)
  583. fugit (~> 1.1, >= 1.1.6)
  584. safety_net_attestation (0.4.0)
  585. jwt (~> 2.0)
  586. sanitize (5.2.3)
  587. crass (~> 1.0.2)
  588. nokogiri (>= 1.8.0)
  589. nokogumbo (~> 2.0)
  590. scenic (1.5.4)
  591. activerecord (>= 4.0.0)
  592. railties (>= 4.0.0)
  593. securecompare (1.0.0)
  594. semantic_range (2.3.0)
  595. sidekiq (6.2.0)
  596. connection_pool (>= 2.2.2)
  597. rack (~> 2.0)
  598. redis (>= 4.2.0)
  599. sidekiq-bulk (0.2.0)
  600. sidekiq
  601. sidekiq-scheduler (3.0.1)
  602. e2mmap
  603. redis (>= 3, < 5)
  604. rufus-scheduler (~> 3.2)
  605. sidekiq (>= 3)
  606. thwait
  607. tilt (>= 1.4.0)
  608. sidekiq-unique-jobs (7.0.7)
  609. brpoplpush-redis_script (> 0.1.1, <= 2.0.0)
  610. concurrent-ruby (~> 1.0, >= 1.0.5)
  611. sidekiq (>= 5.0, < 7.0)
  612. thor (>= 0.20, < 2.0)
  613. simple-navigation (4.1.0)
  614. activesupport (>= 2.3.2)
  615. simple_form (5.1.0)
  616. actionpack (>= 5.2)
  617. activemodel (>= 5.2)
  618. simplecov (0.21.2)
  619. docile (~> 1.1)
  620. simplecov-html (~> 0.11)
  621. simplecov_json_formatter (~> 0.1)
  622. simplecov-html (0.12.3)
  623. simplecov_json_formatter (0.1.2)
  624. sprockets (3.7.2)
  625. concurrent-ruby (~> 1.0)
  626. rack (> 1, < 3)
  627. sprockets-rails (3.2.2)
  628. actionpack (>= 4.0)
  629. activesupport (>= 4.0)
  630. sprockets (>= 3.0.0)
  631. sshkit (1.21.2)
  632. net-scp (>= 1.1.2)
  633. net-ssh (>= 2.8.0)
  634. stackprof (0.2.16)
  635. statsd-ruby (1.5.0)
  636. stoplight (2.2.1)
  637. streamio-ffmpeg (3.0.2)
  638. multi_json (~> 1.8)
  639. strong_migrations (0.7.6)
  640. activerecord (>= 5)
  641. temple (0.8.2)
  642. terminal-table (3.0.0)
  643. unicode-display_width (~> 1.1, >= 1.1.1)
  644. terrapin (0.6.0)
  645. climate_control (>= 0.0.3, < 1.0)
  646. thor (1.1.0)
  647. thwait (0.2.0)
  648. e2mmap
  649. tilt (2.0.10)
  650. tpm-key_attestation (0.9.0)
  651. bindata (~> 2.4)
  652. openssl-signature_algorithm (~> 0.4.0)
  653. tty-color (0.6.0)
  654. tty-cursor (0.7.1)
  655. tty-prompt (0.23.0)
  656. pastel (~> 0.8)
  657. tty-reader (~> 0.8)
  658. tty-reader (0.9.0)
  659. tty-cursor (~> 0.7)
  660. tty-screen (~> 0.8)
  661. wisper (~> 2.0)
  662. tty-screen (0.8.1)
  663. twitter-text (3.1.0)
  664. idn-ruby
  665. unf (~> 0.1.0)
  666. tzinfo (2.0.4)
  667. concurrent-ruby (~> 1.0)
  668. tzinfo-data (1.2021.1)
  669. tzinfo (>= 1.0.0)
  670. unf (0.1.4)
  671. unf_ext
  672. unf_ext (0.0.7.7)
  673. unicode-display_width (1.7.0)
  674. uniform_notifier (1.14.1)
  675. warden (1.2.9)
  676. rack (>= 2.0.9)
  677. webauthn (3.0.0.alpha1)
  678. android_key_attestation (~> 0.3.0)
  679. awrence (~> 1.1)
  680. bindata (~> 2.4)
  681. cbor (~> 0.5.9)
  682. cose (~> 1.0)
  683. openssl (~> 2.0)
  684. safety_net_attestation (~> 0.4.0)
  685. securecompare (~> 1.0)
  686. tpm-key_attestation (~> 0.9.0)
  687. webmock (3.12.1)
  688. addressable (>= 2.3.6)
  689. crack (>= 0.3.2)
  690. hashdiff (>= 0.4.0, < 2.0.0)
  691. webpacker (5.2.1)
  692. activesupport (>= 5.2)
  693. rack-proxy (>= 0.6.1)
  694. railties (>= 5.2)
  695. semantic_range (>= 2.3.0)
  696. webpush (0.3.8)
  697. hkdf (~> 0.2)
  698. jwt (~> 2.0)
  699. websocket-driver (0.7.3)
  700. websocket-extensions (>= 0.1.0)
  701. websocket-extensions (0.1.5)
  702. wisper (2.0.1)
  703. xorcist (1.1.2)
  704. xpath (3.2.0)
  705. nokogiri (~> 1.8)