Skip to content

v2.0.35

  • v2.0.35
  • 20d79eb

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    GPG key ID: 4AEE18F83AFDEB23
    Expired
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
v2.0.35: Fix cannot send test message (security update) (#293)
  • v2.0.35
  • 20d79eb

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    GPG key ID: 4AEE18F83AFDEB23
    Expired
    Verified
    Learn about vigilant mode
@GDay GDay tagged this 07 May 00:04 
Full details: https://github.com/chiefonboarding/ChiefOnboarding/pull/293
There was a bug which allowed the user's 2FA secret token to be empty. This was only the case if the user was created through the initial setup wizard which has been introduced on March 28. Running the migration of this commit will fix that, but might not allow a user to pass 2FA (as a new token will be created). Anyone already using ChiefOnboarding before that release is not affected.
Assets 2
Loading