GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — BCrypt::Errors::InvalidSalt: invalid salt when moving data generated by 2.1.4 to 3.0.1 · Issue #38 · bcrypt-ruby/bcrypt-ruby

BCrypt::Errors::InvalidSalt: invalid salt when moving data generated by 2.1.4 to 3.0.1 #38

New issue
Copy link
New issue
Copy link
Open
Open
BCrypt::Errors::InvalidSalt: invalid salt when moving data generated by 2.1.4 to 3.0.1#38
Copy link

Description

@leskiger
leskiger
opened on Dec 5, 2011
Issue body actions

Hello,
I ran head-first into this issue this morning when migrating user data from an app that used bcrypt 2.1.4 to an app that uses bcrypt 3.0.1. It appears the old salts are 20 characters long while the salts generated by 3.0.1 are 29 characters. I'm not sure if there are other differences in format as well. I saw in the changelog that version 3.0.0 moved to a different underlying implementation and I wonder if that's the source issue?

At any rate, I can't seem to find any documentation for migrating salts to the current version. Any assistance would be greatly appreciated.

Thanks
Les

Activity

  1. emiltin commented on Mar 30, 2012

    @emiltin
    emiltin
    on Mar 30, 2012
    More actions

    same problem here, but i suspect there will no way to migrate salts to the new format? if this is true it means all users have to reset their passwords?

  2. emiltin commented on Mar 30, 2012

    @emiltin
    emiltin
    on Mar 30, 2012
    More actions

    is there a way to just keep using the old salts?

  3. tmm1 commented on Mar 31, 2013

    @tmm1
    tmm1
    on Mar 31, 2013
    Collaborator
    More actions

    Did you find a solution to this?

  4. micwoj92 commented on May 26, 2024

    @micwoj92
    micwoj92
    on May 26, 2024
    More actions

    Hello, is this issue still relevant? 3.0.0 released 12 years ago. I doubt solution for this migration problem with come if It wasn't solved in 10+ years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.