Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Changed sha1 into bcrypt#3356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
wouterj wants to merge1 commit into2.2fromsecurity_fix
Closed

Changed sha1 into bcrypt#3356

wouterj wants to merge1 commit into2.2fromsecurity_fix

Conversation

wouterj
Copy link
Member

QA
Doc fix?yes
New docs?no
Applies to2.2+ (bcrypt was introduced in 2.2)
Fixed ticketshttps://twitter.com/ircmaxell/status/412978651123023872

We loose some information, but I don't think that information is necessary. I also made the change without testing it, so: Needs some review!

/cc@ircmaxell@weaverryan

@@ -1358,6 +1358,15 @@ the password is simply run through the ``sha1`` algorithm one time and without
any extra encoding. You can now calculate the hashed password either programmatically
(e.g. ``hash('sha1', 'ryanpass')``) or via some online tool like `functions-online.com`_

.. caution::

The above example is not meaned for practical usage, it uses a weak hash
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I left the above example with sha1, because when using bcrypt it would be hard to get the hashed password.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

is not meant

@Incognito
Copy link
Contributor

A larger change to the docs may be more suitable for the reader.

For example we could move this section to be entirely on use of bcrypt and add an extra page elsewhere that describe pbkdf2 usage, and we can group "legacy hashing" algos like MD5, Rot13, Sha1, etc.

@1ed
Copy link
Contributor

1ed commentedDec 22, 2013

You should add a note about the requirements somewhere. To use the BCrypt encoder, you need to upgrade to PHP 5.5 or install the "ircmaxell/password-compat" via Composer ... seeBCryptPasswordEncoder

weaverryan added a commit that referenced this pull requestJan 2, 2014
… details in intro area that aren't necessary (you'll need to read the cookbook entry for more details anyways)
weaverryan added a commit that referenced this pull requestJan 2, 2014
Also removing one example (now possible with using bcrypt from the beginning) and related tweaks.
weaverryan added a commit that referenced this pull requestJan 2, 2014
Also filling in other details related to using BCrypt
@weaverryan
Copy link
Member

Thanks for starting with Wouter! I've continued the conversation with a new PR at#3405 with some additional changes.

Thanks!

@wouterjwouterj deleted the security_fix branchJanuary 2, 2014 01:03
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@wouterj@Incognito@1ed@weaverryan@xabbuh

[8]ページ先頭

©2009-2025 Movatter.jp