|
|
|
|
GIT
|
|
|
|
|
remote: https://github.com/ianheggie/health_check
|
|
|
|
|
revision: 0b799ead604f900ed50685e9b2d469cd2befba5b
|
|
|
|
|
ref: 0b799ead604f900ed50685e9b2d469cd2befba5b
|
|
|
|
|
specs:
|
|
|
|
|
health_check (4.0.0.pre)
|
|
|
|
|
rails (>= 4.0)
|
|
|
|
|
|
|
|
|
|
GIT
|
|
|
|
|
remote: https://github.com/witgo/nilsimsa
|
|
|
|
|
revision: fd184883048b922b176939f851338d0a4971a532
|
|
|
|
|
ref: fd184883048b922b176939f851338d0a4971a532
|
|
|
|
|
specs:
|
|
|
|
|
nilsimsa (1.1.2)
|
|
|
|
|
|
|
|
|
|
GEM
|
|
|
|
|
remote: https://rubygems.org/
|
|
|
|
|
specs:
|
|
|
|
|
actioncable (5.2.4.4)
|
|
|
|
|
actionpack (= 5.2.4.4)
|
|
|
|
|
nio4r (~> 2.0)
|
|
|
|
|
websocket-driver (>= 0.6.1)
|
|
|
|
|
actionmailer (5.2.4.4)
|
|
|
|
|
actionpack (= 5.2.4.4)
|
|
|
|
|
actionview (= 5.2.4.4)
|
|
|
|
|
activejob (= 5.2.4.4)
|
|
|
|
|
mail (~> 2.5, >= 2.5.4)
|
|
|
|
|
rails-dom-testing (~> 2.0)
|
|
|
|
|
actionpack (5.2.4.4)
|
|
|
|
|
actionview (= 5.2.4.4)
|
|
|
|
|
activesupport (= 5.2.4.4)
|
|
|
|
|
rack (~> 2.0, >= 2.0.8)
|
|
|
|
|
rack-test (>= 0.6.3)
|
|
|
|
|
rails-dom-testing (~> 2.0)
|
|
|
|
|
rails-html-sanitizer (~> 1.0, >= 1.0.2)
|
|
|
|
|
actionview (5.2.4.4)
|
|
|
|
|
activesupport (= 5.2.4.4)
|
|
|
|
|
builder (~> 3.1)
|
|
|
|
|
erubi (~> 1.4)
|
|
|
|
|
rails-dom-testing (~> 2.0)
|
|
|
|
|
rails-html-sanitizer (~> 1.0, >= 1.0.3)
|
|
|
|
|
active_model_serializers (0.10.12)
|
|
|
|
|
actionpack (>= 4.1, < 6.2)
|
|
|
|
|
activemodel (>= 4.1, < 6.2)
|
|
|
|
|
case_transform (>= 0.2)
|
|
|
|
|
jsonapi-renderer (>= 0.1.1.beta1, < 0.3)
|
|
|
|
|
active_record_query_trace (1.8)
|
|
|
|
|
activejob (5.2.4.4)
|
|
|
|
|
activesupport (= 5.2.4.4)
|
|
|
|
|
globalid (>= 0.3.6)
|
|
|
|
|
activemodel (5.2.4.4)
|
|
|
|
|
activesupport (= 5.2.4.4)
|
|
|
|
|
activerecord (5.2.4.4)
|
|
|
|
|
activemodel (= 5.2.4.4)
|
|
|
|
|
activesupport (= 5.2.4.4)
|
|
|
|
|
arel (>= 9.0)
|
|
|
|
|
activestorage (5.2.4.4)
|
|
|
|
|
actionpack (= 5.2.4.4)
|
|
|
|
|
activerecord (= 5.2.4.4)
|
|
|
|
|
marcel (~> 0.3.1)
|
|
|
|
|
activesupport (5.2.4.4)
|
|
|
|
|
concurrent-ruby (~> 1.0, >= 1.0.2)
|
|
|
|
|
i18n (>= 0.7, < 2)
|
|
|
|
|
minitest (~> 5.1)
|
|
|
|
|
tzinfo (~> 1.1)
|
|
|
|
|
addressable (2.7.0)
|
|
|
|
|
public_suffix (>= 2.0.2, < 5.0)
|
|
|
|
|
airbrussh (1.4.0)
|
|
|
|
|
sshkit (>= 1.6.1, != 1.7.0)
|
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>
4 years ago
|
|
|
android_key_attestation (0.3.0)
|
|
|
|
|
annotate (3.1.1)
|
|
|
|
|
activerecord (>= 3.2, < 7.0)
|
|
|
|
|
rake (>= 10.4, < 14.0)
|
|
|
|
|
arel (9.0.0)
|
|
|
|
|
ast (2.4.1)
|
|
|
|
|
attr_encrypted (3.1.0)
|
|
|
|
|
encryptor (~> 3.0.0)
|
|
|
|
|
av (0.9.0)
|
|
|
|
|
cocaine (~> 0.5.3)
|
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>
4 years ago
|
|
|
awrence (1.1.1)
|
|
|
|
|
aws-eventstream (1.1.0)
|
|
|
|
|
aws-partitions (1.424.0)
|
|
|
|
|
aws-sdk-core (3.112.0)
|
|
|
|
|
aws-eventstream (~> 1, >= 1.0.2)
|
|
|
|
|
aws-partitions (~> 1, >= 1.239.0)
|
|
|
|
|
aws-sigv4 (~> 1.1)
|
|
|
|
|
jmespath (~> 1.0)
|
|
|
|
|
aws-sdk-kms (1.42.0)
|
|
|
|
|
aws-sdk-core (~> 3, >= 3.112.0)
|
|
|
|
|
aws-sigv4 (~> 1.1)
|
|
|
|
|
aws-sdk-s3 (1.88.0)
|
|
|
|
|
aws-sdk-core (~> 3, >= 3.112.0)
|
|
|
|
|
aws-sdk-kms (~> 1)
|
|
|
|
|
aws-sigv4 (~> 1.1)
|
|
|
|
|
aws-sigv4 (1.2.2)
|
|
|
|
|
aws-eventstream (~> 1, >= 1.0.2)
|
|
|
|
|
bcrypt (3.1.16)
|
|
|
|
|
better_errors (2.9.1)
|
|
|
|
|
coderay (>= 1.0.0)
|
|
|
|
|
erubi (>= 1.0.0)
|
|
|
|
|
rack (>= 0.9.0)
|
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>
4 years ago
|
|
|
bindata (2.4.8)
|
|
|
|
|
binding_of_caller (1.0.0)
|
|
|
|
|
debug_inspector (>= 0.0.1)
|
|
|
|
|
blurhash (0.1.4)
|
|
|
|
|
ffi (~> 1.10.0)
|
|
|
|
|
bootsnap (1.7.1)
|
|
|
|
|
msgpack (~> 1.0)
|
|
|
|
|
brakeman (4.10.1)
|
|
|
|
|
browser (4.2.0)
|
|
|
|
|
builder (3.2.4)
|
|
|
|
|
bullet (6.1.3)
|
|
|
|
|
activesupport (>= 3.0.0)
|
|
|
|
|
uniform_notifier (~> 1.11)
|
|
|
|
|
bundler-audit (0.7.0.1)
|
|
|
|
|
bundler (>= 1.2.0, < 3)
|
|
|
|
|
thor (>= 0.18, < 2)
|
|
|
|
|
byebug (11.1.3)
|
|
|
|
|
capistrano (3.15.0)
|
|
|
|
|
airbrussh (>= 1.0.0)
|
|
|
|
|
i18n
|
|
|
|
|
rake (>= 10.0.0)
|
|
|
|
|
sshkit (>= 1.9.0)
|
|
|
|
|
capistrano-bundler (2.0.1)
|
|
|
|
|
capistrano (~> 3.1)
|
|
|
|
|
capistrano-rails (1.6.1)
|
|
|
|
|
capistrano (~> 3.1)
|
|
|
|
|
capistrano-bundler (>= 1.1, < 3)
|
|
|
|
|
capistrano-rbenv (2.2.0)
|
|
|
|
|
capistrano (~> 3.1)
|
|
|
|
|
sshkit (~> 1.3)
|
|
|
|
|
capistrano-yarn (2.0.2)
|
|
|
|
|
capistrano (~> 3.0)
|
|
|
|
|
capybara (3.35.3)
|
|
|
|
|
addressable
|
|
|
|
|
mini_mime (>= 0.1.3)
|
|
|
|
|
nokogiri (~> 1.8)
|
|
|
|
|
rack (>= 1.6.0)
|
|
|
|
|
rack-test (>= 0.6.3)
|
|
|
|
|
regexp_parser (>= 1.5, < 3.0)
|
|
|
|
|
xpath (~> 3.2)
|
|
|
|
|
case_transform (0.2)
|
|
|
|
|
activesupport
|
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>
4 years ago
|
|
|
cbor (0.5.9.6)
|
|
|
|
|
charlock_holmes (0.7.7)
|
|
|
|
|
chewy (5.2.0)
|
|
|
|
|
activesupport (>= 5.2)
|
|
|
|
|
elasticsearch (>= 2.0.0)
|
|
|
|
|
elasticsearch-dsl
|
|
|
|
|
chunky_png (1.3.15)
|
|
|
|
|
cld3 (3.4.1)
|
|
|
|
|
ffi (>= 1.1.0, < 1.15.0)
|
|
|
|
|
climate_control (0.2.0)
|
|
|
|
|
cocaine (0.5.8)
|
|
|
|
|
climate_control (>= 0.0.3, < 1.0)
|
|
|
|
|
coderay (1.1.3)
|
|
|
|
|
color_diff (0.1)
|
|
|
|
|
concurrent-ruby (1.1.8)
|
|
|
|
|
connection_pool (2.2.3)
|
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>
4 years ago
|
|
|
cose (1.0.0)
|
|
|
|
|
cbor (~> 0.5.9)
|
|
|
|
|
openssl-signature_algorithm (~> 0.4.0)
|
|
|
|
|
crack (0.4.5)
|
|
|
|
|
rexml
|
|
|
|
|
crass (1.0.6)
|
|
|
|
|
css_parser (1.7.1)
|
|
|
|
|
addressable
|
|
|
|
|
debug_inspector (1.0.0)
|
|
|
|
|
devise (4.7.3)
|
|
|
|
|
bcrypt (~> 3.0)
|
|
|
|
|
orm_adapter (~> 0.1)
|
|
|
|
|
railties (>= 4.1.0)
|
|
|
|
|
responders
|
|
|
|
|
warden (~> 1.2.3)
|
|
|
|
|
devise-two-factor (3.1.0)
|
|
|
|
|
activesupport (< 6.1)
|
|
|
|
|
attr_encrypted (>= 1.3, < 4, != 2)
|
|
|
|
|
devise (~> 4.0)
|
|
|
|
|
railties (< 6.1)
|
|
|
|
|
rotp (~> 2.0)
|
|
|
|
|
devise_pam_authenticatable2 (9.2.0)
|
|
|
|
|
devise (>= 4.0.0)
|
|
|
|
|
rpam2 (~> 4.0)
|
|
|
|
|
diff-lcs (1.4.4)
|
|
|
|
|
discard (1.2.0)
|
|
|
|
|
activerecord (>= 4.2, < 7)
|
|
|
|
|
docile (1.3.4)
|
|
|
|
|
domain_name (0.5.20190701)
|
|
|
|
|
unf (>= 0.0.5, < 1.0.0)
|
|
|
|
|
doorkeeper (5.4.0)
|
|
|
|
|
railties (>= 5)
|
|
|
|
|
dotenv (2.7.6)
|
|
|
|
|
dotenv-rails (2.7.6)
|
|
|
|
|
dotenv (= 2.7.6)
|
|
|
|
|
railties (>= 3.2)
|
|
|
|
|
e2mmap (0.1.0)
|
|
|
|
|
ed25519 (1.2.4)
|
|
|
|
|
elasticsearch (7.10.1)
|
|
|
|
|
elasticsearch-api (= 7.10.1)
|
|
|
|
|
elasticsearch-transport (= 7.10.1)
|
|
|
|
|
elasticsearch-api (7.10.1)
|
|
|
|
|
multi_json
|
|
|
|
|
elasticsearch-dsl (0.1.9)
|
|
|
|
|
elasticsearch-transport (7.10.1)
|
|
|
|
|
faraday (~> 1)
|
|
|
|
|
multi_json
|
|
|
|
|
encryptor (3.0.0)
|
|
|
|
|
erubi (1.10.0)
|
|
|
|
|
et-orbi (1.2.4)
|
|
|
|
|
tzinfo
|
|
|
|
|
excon (0.76.0)
|
|
|
|
|
fabrication (2.21.1)
|
|
|
|
|
faker (2.15.1)
|
|
|
|
|
i18n (>= 1.6, < 2)
|
|
|
|
|
faraday (1.3.0)
|
|
|
|
|
faraday-net_http (~> 1.0)
|
|
|
|
|
multipart-post (>= 1.2, < 3)
|
|
|
|
|
ruby2_keywords
|
|
|
|
|
faraday-net_http (1.0.1)
|
|
|
|
|
fast_blank (1.0.0)
|
|
|
|
|
fastimage (2.2.2)
|
|
|
|
|
ffi (1.10.0)
|
|
|
|
|
ffi-compiler (1.0.1)
|
|
|
|
|
ffi (>= 1.0.0)
|
|
|
|
|
rake
|
|
|
|
|
fog-core (2.1.0)
|
|
|
|
|
builder
|
|
|
|
|
excon (~> 0.58)
|
|
|
|
|
formatador (~> 0.2)
|
|
|
|
|
mime-types
|
|
|
|
|
fog-json (1.2.0)
|
|
|
|
|
fog-core
|
|
|
|
|
multi_json (~> 1.10)
|
|
|
|
|
fog-openstack (0.3.10)
|
|
|
|
|
fog-core (>= 1.45, <= 2.1.0)
|
|
|
|
|
fog-json (>= 1.0)
|
|
|
|
|
ipaddress (>= 0.8)
|
|
|
|
|
formatador (0.2.5)
|
|
|
|
|
fugit (1.3.9)
|
|
|
|
|
et-orbi (~> 1.1, >= 1.1.8)
|
|
|
|
|
raabro (~> 1.3)
|
|
|
|
|
fuubar (2.5.1)
|
|
|
|
|
rspec-core (~> 3.0)
|
|
|
|
|
ruby-progressbar (~> 1.4)
|
|
|
|
|
globalid (0.4.2)
|
|
|
|
|
activesupport (>= 4.2.0)
|
|
|
|
|
hamlit (2.13.0)
|
|
|
|
|
temple (>= 0.8.2)
|
|
|
|
|
thor
|
|
|
|
|
tilt
|
|
|
|
|
hamlit-rails (0.2.3)
|
|
|
|
|
actionpack (>= 4.0.1)
|
|
|
|
|
activesupport (>= 4.0.1)
|
|
|
|
|
hamlit (>= 1.2.0)
|
|
|
|
|
railties (>= 4.0.1)
|
|
|
|
|
hamster (3.0.0)
|
|
|
|
|
concurrent-ruby (~> 1.0)
|
|
|
|
|
hashdiff (1.0.1)
|
|
|
|
|
hashie (4.1.0)
|
|
|
|
|
highline (2.0.3)
|
|
|
|
|
hiredis (0.6.3)
|
|
|
|
|
hkdf (0.3.0)
|
|
|
|
|
htmlentities (4.3.4)
|
|
|
|
|
http (4.4.1)
|
|
|
|
|
addressable (~> 2.3)
|
|
|
|
|
http-cookie (~> 1.0)
|
|
|
|
|
http-form_data (~> 2.2)
|
|
|
|
|
http-parser (~> 1.2.0)
|
|
|
|
|
http-cookie (1.0.3)
|
|
|
|
|
domain_name (~> 0.5)
|
|
|
|
|
http-form_data (2.3.0)
|
|
|
|
|
http-parser (1.2.1)
|
|
|
|
|
ffi-compiler (>= 1.0, < 2.0)
|
|
|
|
|
http_accept_language (2.1.1)
|
|
|
|
|
httplog (1.4.3)
|
|
|
|
|
rack (>= 1.0)
|
|
|
|
|
rainbow (>= 2.0.0)
|
|
|
|
|
i18n (1.8.8)
|
|
|
|
|
concurrent-ruby (~> 1.0)
|
|
|
|
|
i18n-tasks (0.9.33)
|
|
|
|
|
activesupport (>= 4.0.2)
|
|
|
|
|
ast (>= 2.1.0)
|
|
|
|
|
erubi
|
|
|
|
|
highline (>= 2.0.0)
|
|
|
|
|
i18n
|
|
|
|
|
parser (>= 2.2.3.0)
|
|
|
|
|
rails-i18n
|
|
|
|
|
rainbow (>= 2.2.2, < 4.0)
|
|
|
|
|
terminal-table (>= 1.5.1)
|
|
|
|
|
idn-ruby (0.1.0)
|
|
|
|
|
ipaddress (0.8.3)
|
|
|
|
|
iso-639 (0.3.5)
|
|
|
|
|
jmespath (1.4.0)
|
|
|
|
|
json (2.3.1)
|
|
|
|
|
json-canonicalization (0.2.0)
|
|
|
|
|
json-ld (3.1.8)
|
|
|
|
|
htmlentities (~> 4.3)
|
|
|
|
|
json-canonicalization (~> 0.2)
|
|
|
|
|
link_header (~> 0.0, >= 0.0.8)
|
|
|
|
|
multi_json (~> 1.14)
|
|
|
|
|
rack (~> 2.0)
|
|
|
|
|
rdf (~> 3.1)
|
|
|
|
|
json-ld-preloaded (3.1.4)
|
|
|
|
|
json-ld (~> 3.1)
|
|
|
|
|
rdf (~> 3.1)
|
|
|
|
|
jsonapi-renderer (0.2.2)
|
|
|
|
|
jwt (2.2.2)
|
|
|
|
|
kaminari (1.2.1)
|
|
|
|
|
activesupport (>= 4.1.0)
|
|
|
|
|
kaminari-actionview (= 1.2.1)
|
|
|
|
|
kaminari-activerecord (= 1.2.1)
|
|
|
|
|
kaminari-core (= 1.2.1)
|
|
|
|
|
kaminari-actionview (1.2.1)
|
|
|
|
|
actionview
|
|
|
|
|
kaminari-core (= 1.2.1)
|
|
|
|
|
kaminari-activerecord (1.2.1)
|
|
|
|
|
activerecord
|
|
|
|
|
kaminari-core (= 1.2.1)
|
|
|
|
|
kaminari-core (1.2.1)
|
|
|
|
|
launchy (2.5.0)
|
|
|
|
|
addressable (~> 2.7)
|
|
|
|
|
letter_opener (1.7.0)
|
|
|
|
|
launchy (~> 2.2)
|
|
|
|
|
letter_opener_web (1.4.0)
|
|
|
|
|
actionmailer (>= 3.2)
|
|
|
|
|
letter_opener (~> 1.0)
|
|
|
|
|
railties (>= 3.2)
|
Fix #24 - Thread resolving for remote statuses
This is a big one, so let me enumerate:
Accounts as well as stream entry pages now contain Link headers that
reference the Atom feed and Webfinger URL for the former and Atom entry
for the latter. So you only need to HEAD those resources to get that
information, no need to download and parse HTML <link>s.
ProcessFeedService will now queue ThreadResolveWorker for each remote
status that it cannot find otherwise. Furthermore, entries are now
processed in reverse order (from bottom to top) in case a newer entry
references a chronologically previous one.
ThreadResolveWorker uses FetchRemoteStatusService to obtain a status
and attach the child status it was queued for to it.
FetchRemoteStatusService looks up the URL, first with a HEAD, tests
if it's an Atom feed, in which case it processes it directly. Next
for Link headers to the Atom feed, in which case that is fetched
and processed. Lastly if it's HTML, it is checked for <link>s to the Atom
feed, and if such is found, that is fetched and processed. The account for
the status is derived from author/name attribute in the XML and the hostname
in the URL (domain). FollowRemoteAccountService and ProcessFeedService
are used.
This means that potentially threads are resolved recursively until a dead-end
is encountered, however it is performed asynchronously over background jobs,
so it should be ok.
8 years ago
|
|
|
link_header (0.0.8)
|
|
|
|
|
lograge (0.11.2)
|
|
|
|
|
actionpack (>= 4)
|
|
|
|
|
activesupport (>= 4)
|
|
|
|
|
railties (>= 4)
|
|
|
|
|
request_store (~> 1.0)
|
|
|
|
|
loofah (2.8.0)
|
|
|
|
|
crass (~> 1.0.2)
|
|
|
|
|
nokogiri (>= 1.5.9)
|
|
|
|
|
mail (2.7.1)
|
|
|
|
|
mini_mime (>= 0.1.1)
|
|
|
|
|
makara (0.5.0)
|
|
|
|
|
activerecord (>= 3.0.0)
|
|
|
|
|
marcel (0.3.3)
|
|
|
|
|
mimemagic (~> 0.3.2)
|
|
|
|
|
mario-redis-lock (1.2.1)
|
|
|
|
|
redis (>= 3.0.5)
|
|
|
|
|
memory_profiler (1.0.0)
|
|
|
|
|
method_source (1.0.0)
|
|
|
|
|
microformats (4.2.1)
|
|
|
|
|
json (~> 2.2)
|
|
|
|
|
nokogiri (~> 1.10)
|
|
|
|
|
mime-types (3.3.1)
|
|
|
|
|
mime-types-data (~> 3.2015)
|
|
|
|
|
mime-types-data (3.2020.0512)
|
|
|
|
|
mimemagic (0.3.5)
|
|
|
|
|
mini_mime (1.0.2)
|
|
|
|
|
mini_portile2 (2.5.0)
|
|
|
|
|
minitest (5.14.3)
|
|
|
|
|
msgpack (1.4.2)
|
|
|
|
|
multi_json (1.15.0)
|
|
|
|
|
multipart-post (2.1.1)
|
|
|
|
|
net-ldap (0.17.0)
|
|
|
|
|
net-scp (3.0.0)
|
|
|
|
|
net-ssh (>= 2.6.5, < 7.0.0)
|
|
|
|
|
net-ssh (6.1.0)
|
|
|
|
|
nio4r (2.5.4)
|
|
|
|
|
nokogiri (1.11.1)
|
|
|
|
|
mini_portile2 (~> 2.5.0)
|
|
|
|
|
racc (~> 1.4)
|
|
|
|
|
nokogumbo (2.0.4)
|
|
|
|
|
nokogiri (~> 1.8, >= 1.8.4)
|
|
|
|
|
nsa (0.2.7)
|
|
|
|
|
activesupport (>= 4.2, < 6)
|
|
|
|
|
concurrent-ruby (~> 1.0, >= 1.0.2)
|
|
|
|
|
sidekiq (>= 3.5)
|
|
|
|
|
statsd-ruby (~> 1.4, >= 1.4.0)
|
|
|
|
|
oj (3.11.2)
|
|
|
|
|
omniauth (1.9.1)
|
|
|
|
|
hashie (>= 3.4.6)
|
|
|
|
|
rack (>= 1.6.2, < 3)
|
|
|
|
|
omniauth-cas (2.0.0)
|
|
|
|
|
addressable (~> 2.3)
|
|
|
|
|
nokogiri (~> 1.5)
|
|
|
|
|
omniauth (~> 1.2)
|
|
|
|
|
omniauth-rails_csrf_protection (0.1.2)
|
|
|
|
|
actionpack (>= 4.2)
|
|
|
|
|
omniauth (>= 1.3.1)
|
|
|
|
|
omniauth-saml (1.10.3)
|
|
|
|
|
omniauth (~> 1.3, >= 1.3.2)
|
|
|
|
|
ruby-saml (~> 1.9)
|
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>
4 years ago
|
|
|
openssl (2.2.0)
|
|
|
|
|
openssl-signature_algorithm (0.4.0)
|
|
|
|
|
orm_adapter (0.5.0)
|
|
|
|
|
ox (2.14.1)
|
|
|
|
|
paperclip (6.0.0)
|
|
|
|
|
activemodel (>= 4.2.0)
|
|
|
|
|
activesupport (>= 4.2.0)
|
|
|
|
|
mime-types
|
|
|
|
|
mimemagic (~> 0.3.0)
|
|
|
|
|
terrapin (~> 0.6.0)
|
|
|
|
|
paperclip-av-transcoder (0.6.4)
|
|
|
|
|
av (~> 0.9.0)
|
|
|
|
|
paperclip (>= 2.5.2)
|
|
|
|
|
parallel (1.20.1)
|
|
|
|
|
parallel_tests (3.4.0)
|
|
|
|
|
parallel
|
|
|
|
|
parser (3.0.0.0)
|
|
|
|
|
ast (~> 2.4.1)
|
|
|
|
|
parslet (2.0.0)
|
|
|
|
|
pastel (0.8.0)
|
|
|
|
|
tty-color (~> 0.5)
|
|
|
|
|
pg (1.2.3)
|
|
|
|
|
pghero (2.7.4)
|
|
|
|
|
activerecord (>= 5)
|
|
|
|
|
pkg-config (1.4.5)
|
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
4 years ago
|
|
|
pluck_each (0.1.3)
|
|
|
|
|
activerecord (> 3.2.0)
|
|
|
|
|
activesupport (> 3.0.0)
|
|
|
|
|
posix-spawn (0.3.15)
|
|
|
|
|
premailer (1.14.2)
|
|
|
|
|
addressable
|
|
|
|
|
css_parser (>= 1.6.0)
|
|
|
|
|
htmlentities (>= 4.0.0)
|
|
|
|
|
premailer-rails (1.11.1)
|
|
|
|
|
actionmailer (>= 3)
|
|
|
|
|
premailer (~> 1.7, >= 1.7.9)
|
|
|
|
|
private_address_check (0.5.0)
|
|
|
|
|
pry (0.13.1)
|
|
|
|
|
coderay (~> 1.1)
|
|
|
|
|
method_source (~> 1.0)
|
|
|
|
|
pry-byebug (3.9.0)
|
|
|
|
|
byebug (~> 11.0)
|
|
|
|
|
pry (~> 0.13.0)
|
|
|
|
|
pry-rails (0.3.9)
|
|
|
|
|
pry (>= 0.10.4)
|
|
|
|
|
public_suffix (4.0.6)
|
|
|
|
|
puma (5.1.1)
|
|
|
|
|
nio4r (~> 2.0)
|
|
|
|
|
pundit (2.1.0)
|
|
|
|
|
activesupport (>= 3.0.0)
|
|
|
|
|
raabro (1.3.3)
|
|
|
|
|
racc (1.5.2)
|
|
|
|
|
rack (2.2.3)
|
|
|
|
|
rack-attack (6.4.0)
|
|
|
|
|
rack (>= 1.0, < 3)
|
|
|
|
|
rack-cors (1.1.1)
|
|
|
|
|
rack (>= 2.0.0)
|
|
|
|
|
rack-proxy (0.6.5)
|
|
|
|
|
rack
|
|
|
|
|
rack-test (1.1.0)
|
|
|
|
|
rack (>= 1.0, < 3)
|
|
|
|
|
rails (5.2.4.4)
|
|
|
|
|
actioncable (= 5.2.4.4)
|
|
|
|
|
actionmailer (= 5.2.4.4)
|
|
|
|
|
actionpack (= 5.2.4.4)
|
|
|
|
|
actionview (= 5.2.4.4)
|
|
|
|
|
activejob (= 5.2.4.4)
|
|
|
|
|
activemodel (= 5.2.4.4)
|
|
|
|
|
activerecord (= 5.2.4.4)
|
|
|
|
|
activestorage (= 5.2.4.4)
|
|
|
|
|
activesupport (= 5.2.4.4)
|
|
|
|
|
bundler (>= 1.3.0)
|
|
|
|
|
railties (= 5.2.4.4)
|
|
|
|
|
sprockets-rails (>= 2.0.0)
|
|
|
|
|
rails-controller-testing (1.0.5)
|
|
|
|
|
actionpack (>= 5.0.1.rc1)
|
|
|
|
|
actionview (>= 5.0.1.rc1)
|
|
|
|
|
activesupport (>= 5.0.1.rc1)
|
|
|
|
|
rails-dom-testing (2.0.3)
|
|
|
|
|
activesupport (>= 4.2.0)
|
|
|
|
|
nokogiri (>= 1.6)
|
|
|
|
|
rails-html-sanitizer (1.3.0)
|
|
|
|
|
loofah (~> 2.3)
|
|
|
|
|
rails-i18n (5.1.3)
|
|
|
|
|
i18n (>= 0.7, < 2)
|
|
|
|
|
railties (>= 5.0, < 6)
|
|
|
|
|
rails-settings-cached (0.6.6)
|
|
|
|
|
rails (>= 4.2.0)
|
|
|
|
|
railties (5.2.4.4)
|
|
|
|
|
actionpack (= 5.2.4.4)
|
|
|
|
|
activesupport (= 5.2.4.4)
|
|
|
|
|
method_source
|
|
|
|
|
rake (>= 0.8.7)
|
|
|
|
|
thor (>= 0.19.0, < 2.0)
|
|
|
|
|
rainbow (3.0.0)
|
|
|
|
|
rake (13.0.3)
|
|
|
|
|
rdf (3.1.10)
|
|
|
|
|
hamster (~> 3.0)
|
|
|
|
|
link_header (~> 0.0, >= 0.0.8)
|
|
|
|
|
rdf-normalize (0.4.0)
|
|
|
|
|
rdf (~> 3.1)
|
|
|
|
|
redis (4.2.5)
|
|
|
|
|
redis-actionpack (5.2.0)
|
|
|
|
|
actionpack (>= 5, < 7)
|
|
|
|
|
redis-rack (>= 2.1.0, < 3)
|
|
|
|
|
redis-store (>= 1.1.0, < 2)
|
|
|
|
|
redis-activesupport (5.2.0)
|
|
|
|
|
activesupport (>= 3, < 7)
|
|
|
|
|
redis-store (>= 1.3, < 2)
|
|
|
|
|
redis-namespace (1.8.0)
|
|
|
|
|
redis (>= 3.0.4)
|
|
|
|
|
redis-rack (2.1.3)
|
|
|
|
|
rack (>= 2.0.8, < 3)
|
|
|
|
|
redis-store (>= 1.2, < 2)
|
|
|
|
|
redis-rails (5.0.2)
|
|
|
|
|
redis-actionpack (>= 5.0, < 6)
|
|
|
|
|
redis-activesupport (>= 5.0, < 6)
|
|
|
|
|
redis-store (>= 1.2, < 2)
|
|
|
|
|
redis-store (1.9.0)
|
|
|
|
|
redis (>= 4, < 5)
|
|
|
|
|
regexp_parser (2.0.3)
|
|
|
|
|
request_store (1.5.0)
|
|
|
|
|
rack (>= 1.4)
|
|
|
|
|
responders (3.0.1)
|
|
|
|
|
actionpack (>= 5.0)
|
|
|
|
|
railties (>= 5.0)
|
|
|
|
|
rexml (3.2.4)
|
|
|
|
|
rotp (2.1.2)
|
|
|
|
|
rpam2 (4.0.2)
|
|
|
|
|
rqrcode (1.2.0)
|
|
|
|
|
chunky_png (~> 1.0)
|
|
|
|
|
rqrcode_core (~> 0.2)
|
|
|
|
|
rqrcode_core (0.2.0)
|
|
|
|
|
rspec-core (3.10.1)
|
|
|
|
|
rspec-support (~> 3.10.0)
|
|
|
|
|
rspec-expectations (3.10.1)
|
|
|
|
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
|
|
|
rspec-support (~> 3.10.0)
|
|
|
|
|
rspec-mocks (3.10.1)
|
|
|
|
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
|
|
|
rspec-support (~> 3.10.0)
|
|
|
|
|
rspec-rails (4.0.2)
|
|
|
|
|
actionpack (>= 4.2)
|
|
|
|
|
activesupport (>= 4.2)
|
|
|
|
|
railties (>= 4.2)
|
|
|
|
|
rspec-core (~> 3.10)
|
|
|
|
|
rspec-expectations (~> 3.10)
|
|
|
|
|
rspec-mocks (~> 3.10)
|
|
|
|
|
rspec-support (~> 3.10)
|
|
|
|
|
rspec-sidekiq (3.1.0)
|
|
|
|
|
rspec-core (~> 3.0, >= 3.0.0)
|
|
|
|
|
sidekiq (>= 2.4.0)
|
|
|
|
|
rspec-support (3.10.1)
|
|
|
|
|
rspec_junit_formatter (0.4.1)
|
|
|
|
|
rspec-core (>= 2, < 4, != 2.12.0)
|
|
|
|
|
rubocop (1.8.1)
|
|
|
|
|
parallel (~> 1.10)
|
|
|
|
|
parser (>= 3.0.0.0)
|
|
|
|
|
rainbow (>= 2.2.2, < 4.0)
|
|
|
|
|
regexp_parser (>= 1.8, < 3.0)
|
|
|
|
|
rexml
|
|
|
|
|
rubocop-ast (>= 1.2.0, < 2.0)
|
|
|
|
|
ruby-progressbar (~> 1.7)
|
|
|
|
|
unicode-display_width (>= 1.4.0, < 3.0)
|
|
|
|
|
rubocop-ast (1.4.0)
|
|
|
|
|
parser (>= 2.7.1.5)
|
|
|
|
|
rubocop-rails (2.9.1)
|
|
|
|
|
activesupport (>= 4.2.0)
|
|
|
|
|
rack (>= 1.1)
|
|
|
|
|
rubocop (>= 0.90.0, < 2.0)
|
|
|
|
|
ruby-progressbar (1.11.0)
|
|
|
|
|
ruby-saml (1.11.0)
|
|
|
|
|
nokogiri (>= 1.5.10)
|
|
|
|
|
ruby2_keywords (0.0.4)
|
|
|
|
|
rufus-scheduler (3.6.0)
|
|
|
|
|
fugit (~> 1.1, >= 1.1.6)
|
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>
4 years ago
|
|
|
safety_net_attestation (0.4.0)
|
|
|
|
|
jwt (~> 2.0)
|
|
|
|
|
sanitize (5.2.3)
|
|
|
|
|
crass (~> 1.0.2)
|
|
|
|
|
nokogiri (>= 1.8.0)
|
|
|
|
|
nokogumbo (~> 2.0)
|
|
|
|
|
scenic (1.5.4)
|
|
|
|
|
activerecord (>= 4.0.0)
|
|
|
|
|
railties (>= 4.0.0)
|
|
|
|
|
secure_headers (3.9.0)
|
|
|
|
|
useragent
|
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>
4 years ago
|
|
|
securecompare (1.0.0)
|
|
|
|
|
semantic_range (2.3.0)
|
|
|
|
|
sidekiq (6.1.3)
|
|
|
|
|
connection_pool (>= 2.2.2)
|
|
|
|
|
rack (~> 2.0)
|
|
|
|
|
redis (>= 4.2.0)
|
|
|
|
|
sidekiq-bulk (0.2.0)
|
|
|
|
|
sidekiq
|
|
|
|
|
sidekiq-scheduler (3.0.1)
|
|
|
|
|
e2mmap
|
|
|
|
|
redis (>= 3, < 5)
|
|
|
|
|
rufus-scheduler (~> 3.2)
|
|
|
|
|
sidekiq (>= 3)
|
|
|
|
|
thwait
|
|
|
|
|
tilt (>= 1.4.0)
|
|
|
|
|
sidekiq-unique-jobs (6.0.25)
|
|
|
|
|
concurrent-ruby (~> 1.0, >= 1.0.5)
|
|
|
|
|
sidekiq (>= 4.0, < 7.0)
|
|
|
|
|
thor (>= 0.20, < 2.0)
|
|
|
|
|
simple-navigation (4.1.0)
|
|
|
|
|
activesupport (>= 2.3.2)
|
|
|
|
|
simple_form (5.0.3)
|
|
|
|
|
actionpack (>= 5.0)
|
|
|
|
|
activemodel (>= 5.0)
|
|
|
|
|
simplecov (0.21.2)
|
|
|
|
|
docile (~> 1.1)
|
|
|
|
|
simplecov-html (~> 0.11)
|
|
|
|
|
simplecov_json_formatter (~> 0.1)
|
|
|
|
|
simplecov-html (0.12.3)
|
|
|
|
|
simplecov_json_formatter (0.1.2)
|
|
|
|
|
sprockets (3.7.2)
|
|
|
|
|
concurrent-ruby (~> 1.0)
|
|
|
|
|
rack (> 1, < 3)
|
|
|
|
|
sprockets-rails (3.2.2)
|
|
|
|
|
actionpack (>= 4.0)
|
|
|
|
|
activesupport (>= 4.0)
|
|
|
|
|
sprockets (>= 3.0.0)
|
|
|
|
|
sshkit (1.21.1)
|
|
|
|
|
net-scp (>= 1.1.2)
|
|
|
|
|
net-ssh (>= 2.8.0)
|
|
|
|
|
stackprof (0.2.16)
|
|
|
|
|
statsd-ruby (1.4.0)
|
|
|
|
|
stoplight (2.2.1)
|
|
|
|
|
streamio-ffmpeg (3.0.2)
|
|
|
|
|
multi_json (~> 1.8)
|
|
|
|
|
strong_migrations (0.7.6)
|
|
|
|
|
activerecord (>= 5)
|
|
|
|
|
temple (0.8.2)
|
|
|
|
|
terminal-table (2.0.0)
|
|
|
|
|
unicode-display_width (~> 1.1, >= 1.1.1)
|
|
|
|
|
terrapin (0.6.0)
|
|
|
|
|
climate_control (>= 0.0.3, < 1.0)
|
|
|
|
|
thor (1.1.0)
|
|
|
|
|
thread_safe (0.3.6)
|
|
|
|
|
thwait (0.2.0)
|
|
|
|
|
e2mmap
|
|
|
|
|
tilt (2.0.10)
|
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>
4 years ago
|
|
|
tpm-key_attestation (0.9.0)
|
|
|
|
|
bindata (~> 2.4)
|
|
|
|
|
openssl-signature_algorithm (~> 0.4.0)
|
|
|
|
|
tty-color (0.6.0)
|
|
|
|
|
tty-cursor (0.7.1)
|
|
|
|
|
tty-prompt (0.23.0)
|
|
|
|
|
pastel (~> 0.8)
|
|
|
|
|
tty-reader (~> 0.8)
|
|
|
|
|
tty-reader (0.9.0)
|
|
|
|
|
tty-cursor (~> 0.7)
|
|
|
|
|
tty-screen (~> 0.8)
|
|
|
|
|
wisper (~> 2.0)
|
|
|
|
|
tty-screen (0.8.1)
|
|
|
|
|
twitter-text (1.14.7)
|
|
|
|
|
unf (~> 0.1.0)
|
|
|
|
|
tzinfo (1.2.9)
|
|
|
|
|
thread_safe (~> 0.1)
|
|
|
|
|
tzinfo-data (1.2021.1)
|
|
|
|
|
tzinfo (>= 1.0.0)
|
|
|
|
|
unf (0.1.4)
|
|
|
|
|
unf_ext
|
|
|
|
|
unf_ext (0.0.7.7)
|
|
|
|
|
unicode-display_width (1.7.0)
|
|
|
|
|
uniform_notifier (1.13.2)
|
|
|
|
|
useragent (0.16.10)
|
|
|
|
|
warden (1.2.9)
|
|
|
|
|
rack (>= 2.0.9)
|
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>
4 years ago
|
|
|
webauthn (3.0.0.alpha1)
|
|
|
|
|
android_key_attestation (~> 0.3.0)
|
|
|
|
|
awrence (~> 1.1)
|
|
|
|
|
bindata (~> 2.4)
|
|
|
|
|
cbor (~> 0.5.9)
|
|
|
|
|
cose (~> 1.0)
|
|
|
|
|
openssl (~> 2.0)
|
|
|
|
|
safety_net_attestation (~> 0.4.0)
|
|
|
|
|
securecompare (~> 1.0)
|
|
|
|
|
tpm-key_attestation (~> 0.9.0)
|
|
|
|
|
webmock (3.11.2)
|
|
|
|
|
addressable (>= 2.3.6)
|
|
|
|
|
crack (>= 0.3.2)
|
|
|
|
|
hashdiff (>= 0.4.0, < 2.0.0)
|
|
|
|
|
webpacker (5.2.1)
|
|
|
|
|
activesupport (>= 5.2)
|
|
|
|
|
rack-proxy (>= 0.6.1)
|
|
|
|
|
railties (>= 5.2)
|
|
|
|
|
semantic_range (>= 2.3.0)
|
|
|
|
|
webpush (0.3.8)
|
|
|
|
|
hkdf (~> 0.2)
|
|
|
|
|
jwt (~> 2.0)
|
|
|
|
|
websocket-driver (0.7.3)
|
|
|
|
|
websocket-extensions (>= 0.1.0)
|
|
|
|
|
websocket-extensions (0.1.5)
|
|
|
|
|
wisper (2.0.1)
|
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
4 years ago
|
|
|
xorcist (1.1.2)
|
|
|
|
|
xpath (3.2.0)
|
|
|
|
|
nokogiri (~> 1.8)
|
|
|
|
|
|
|
|
|
|
PLATFORMS
|
|
|
|
|
ruby
|
|
|
|
|
|
|
|
|
|
DEPENDENCIES
|
|
|
|
|
active_model_serializers (~> 0.10)
|
|
|
|
|
active_record_query_trace (~> 1.8)
|
|
|
|
|
addressable (~> 2.7)
|
|
|
|
|
annotate (~> 3.1)
|
|
|
|
|
aws-sdk-s3 (~> 1.88)
|
|
|
|
|
better_errors (~> 2.9)
|
|
|
|
|
binding_of_caller (~> 1.0)
|
|
|
|
|
blurhash (~> 0.1)
|
|
|
|
|
bootsnap (~> 1.7)
|
|
|
|
|
brakeman (~> 4.10)
|
|
|
|
|
browser
|
|
|
|
|
bullet (~> 6.1)
|
|
|
|
|
bundler-audit (~> 0.7)
|
|
|
|
|
capistrano (~> 3.15)
|
|
|
|
|
capistrano-rails (~> 1.6)
|
|
|
|
|
capistrano-rbenv (~> 2.2)
|
|
|
|
|
capistrano-yarn (~> 2.0)
|
|
|
|
|
capybara (~> 3.35)
|
|
|
|
|
charlock_holmes (~> 0.7.7)
|
|
|
|
|
chewy (~> 5.2)
|
|
|
|
|
cld3 (~> 3.4.1)
|
|
|
|
|
climate_control (~> 0.2)
|
|
|
|
|
color_diff (~> 0.1)
|
|
|
|
|
concurrent-ruby
|
|
|
|
|
connection_pool
|
|
|
|
|
devise (~> 4.7)
|
|
|
|
|
devise-two-factor (~> 3.1)
|
|
|
|
|
devise_pam_authenticatable2 (~> 9.2)
|
|
|
|
|
discard (~> 1.2)
|
|
|
|
|
doorkeeper (~> 5.4)
|
|
|
|
|
dotenv-rails (~> 2.7)
|
|
|
|
|
ed25519 (~> 1.2)
|
|
|
|
|
fabrication (~> 2.21)
|
|
|
|
|
faker (~> 2.15)
|
|
|
|
|
fast_blank (~> 1.0)
|
|
|
|
|
fastimage
|
|
|
|
|
fog-core (<= 2.1.0)
|
|
|
|
|
fog-openstack (~> 0.3)
|
|
|
|
|
fuubar (~> 2.5)
|
|
|
|
|
hamlit-rails (~> 0.2)
|
|
|
|
|
health_check!
|
|
|
|
|
hiredis (~> 0.6)
|
|
|
|
|
htmlentities (~> 4.3)
|
|
|
|
|
http (~> 4.4)
|
|
|
|
|
http_accept_language (~> 2.1)
|
|
|
|
|
httplog (~> 1.4.3)
|
|
|
|
|
i18n-tasks (~> 0.9)
|
|
|
|
|
idn-ruby
|
|
|
|
|
iso-639
|
|
|
|
|
json-ld
|
|
|
|
|
json-ld-preloaded (~> 3.1)
|
|
|
|
|
kaminari (~> 1.2)
|
|
|
|
|
letter_opener (~> 1.7)
|
|
|
|
|
letter_opener_web (~> 1.4)
|
|
|
|
|
link_header (~> 0.0)
|
|
|
|
|
lograge (~> 0.11)
|
|
|
|
|
makara (~> 0.5)
|
|
|
|
|
mario-redis-lock (~> 1.2)
|
|
|
|
|
memory_profiler
|
|
|
|
|
microformats (~> 4.2)
|
|
|
|
|
mime-types (~> 3.3.1)
|
|
|
|
|
net-ldap (~> 0.17)
|
|
|
|
|
nilsimsa!
|
|
|
|
|
nokogiri (~> 1.11)
|
|
|
|
|
nsa (~> 0.2)
|
|
|
|
|
oj (~> 3.11)
|
|
|
|
|
omniauth (~> 1.9)
|
|
|
|
|
omniauth-cas (~> 2.0)
|
|
|
|
|
omniauth-rails_csrf_protection (~> 0.1)
|
|
|
|
|
omniauth-saml (~> 1.10)
|
|
|
|
|
ox (~> 2.14)
|
|
|
|
|
paperclip (~> 6.0)
|
|
|
|
|
paperclip-av-transcoder (~> 0.6)
|
|
|
|
|
parallel (~> 1.20)
|
|
|
|
|
parallel_tests (~> 3.4)
|
|
|
|
|
parslet
|
|
|
|
|
pg (~> 1.2)
|
|
|
|
|
pghero (~> 2.7)
|
|
|
|
|
pkg-config (~> 1.4)
|
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
4 years ago
|
|
|
pluck_each (~> 0.1.3)
|
|
|
|
|
posix-spawn
|
|
|
|
|
premailer-rails
|
|
|
|
|
private_address_check (~> 0.5)
|
|
|
|
|
pry-byebug (~> 3.9)
|
|
|
|
|
pry-rails (~> 0.3)
|
|
|
|
|
puma (~> 5.1)
|
|
|
|
|
pundit (~> 2.1)
|
|
|
|
|
rack (~> 2.2.3)
|
|
|
|
|
rack-attack (~> 6.4)
|
|
|
|
|
rack-cors (~> 1.1)
|
|
|
|
|
rails (~> 5.2.4.4)
|
|
|
|
|
rails-controller-testing (~> 1.0)
|
|
|
|
|
rails-i18n (~> 5.1)
|
|
|
|
|
rails-settings-cached (~> 0.6)
|
|
|
|
|
rdf-normalize (~> 0.4)
|
|
|
|
|
redis (~> 4.2)
|
|
|
|
|
redis-namespace (~> 1.8)
|
|
|
|
|
redis-rails (~> 5.0)
|
|
|
|
|
rqrcode (~> 1.2)
|
|
|
|
|
rspec-rails (~> 4.0)
|
|
|
|
|
rspec-sidekiq (~> 3.1)
|
|
|
|
|
rspec_junit_formatter (~> 0.4)
|
|
|
|
|
rubocop (~> 1.8)
|
|
|
|
|
rubocop-rails (~> 2.9)
|
|
|
|
|
ruby-progressbar (~> 1.11)
|
|
|
|
|
sanitize (~> 5.2)
|
|
|
|
|
scenic (~> 1.5)
|
|
|
|
|
secure_headers (~> 3.5)
|
|
|
|
|
sidekiq (~> 6.1)
|
|
|
|
|
sidekiq-bulk (~> 0.2.0)
|
|
|
|
|
sidekiq-scheduler (~> 3.0)
|
|
|
|
|
sidekiq-unique-jobs (~> 6.0)
|
|
|
|
|
simple-navigation (~> 4.1)
|
|
|
|
|
simple_form (~> 5.0)
|
|
|
|
|
simplecov (~> 0.21)
|
|
|
|
|
sprockets (~> 3.7.2)
|
|
|
|
|
sprockets-rails (~> 3.2)
|
|
|
|
|
stackprof
|
|
|
|
|
stoplight (~> 2.2.1)
|
|
|
|
|
streamio-ffmpeg (~> 3.0)
|
|
|
|
|
strong_migrations (~> 0.7)
|
|
|
|
|
thor (~> 1.1)
|
|
|
|
|
tty-prompt (~> 0.23)
|
|
|
|
|
twitter-text (~> 1.14)
|
|
|
|
|
tzinfo-data (~> 1.2021)
|
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>
4 years ago
|
|
|
webauthn (~> 3.0.0.alpha1)
|
|
|
|
|
webmock (~> 3.11)
|
|
|
|
|
webpacker (~> 5.2)
|
|
|
|
|
webpush
|
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
4 years ago
|
|
|
xorcist (~> 1.1)
|
