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

Fail on empty password verification (without warning on any implementation)#35497

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

Merged
fabpot merged 1 commit intosymfony:4.4fromumulmrum:fail-on-empty-password
Feb 3, 2020
Merged

Fail on empty password verification (without warning on any implementation)#35497

fabpot merged 1 commit intosymfony:4.4fromumulmrum:fail-on-empty-password
Feb 3, 2020

Conversation

@umulmrum
Copy link
Contributor

@umulmrumumulmrum commentedJan 28, 2020
edited by javiereguiluz
Loading

QA
Branch?4.4
Bug fix?sort of
New feature?no
Deprecations?no
Tickets
LicenseMIT
Doc PR

When using the sodium extension, an empty $raw string will issue a warning during validation, but the standardpassword_verify() does not. This PR aims to provide identical behavior independent of the underlying implementation. Two assumptions were made (please doublecheck if they are correct):

  • Empty password is never valid.
  • Empty password is not that severe that anybody needs to be informed using a warning or exception.

@nicolas-grekas
Copy link
Member

Can you add the same test case on the SodiumPasswordEncoder?
From your description, I would have expected the patch on SodiumPasswordEncoder btw.
Note that this should target 4.3.
Thanks for the PR.

@umulmrum
Copy link
ContributorAuthor

My description could have been better :-) - without this PR, the call tosodium_crypto_pwhash_str_verify() inNativePasswordEncoder::isPasswordValid() issues the warning, so the change belongs here. Also added it inSodiumPasswordEncoder now - thanks for the pointer.

As for the target branch: The release info onhttps://symfony.com/releases/4.3 already marks 4.3 as security-fixes-only. As this is not a security fix, I targetted 4.4 - which one is correct?

@nicolas-grekas
Copy link
Member

There will be a last 4.3 in a few days.

umulmrum reacted with thumbs up emoji

@umulmrumumulmrum changed the base branch from4.4 to4.3January 28, 2020 14:54
@javiereguiluzjaviereguiluz changed the titleFail on empty password verification (without warning on any implement…Fail on empty password verification (without warning on any implementation)Jan 29, 2020
@nicolas-grekasnicolas-grekas modified the milestones:4.3,4.4Feb 1, 2020
Copy link
Member

@nicolas-grekasnicolas-grekas left a comment

Choose a reason for hiding this comment

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

(for 4.4 now that 4.3 is closed)

{
if ('' ===$raw) {
returnfalse;
}

Choose a reason for hiding this comment

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

there should be a blank line after this one, same below

@fabpotfabpot changed the base branch from4.3 to4.4February 3, 2020 16:30
@fabpot
Copy link
Member

Thank you@umulmrum.

fabpot added a commit that referenced this pull requestFeb 3, 2020
…y implementation) (Stefan Kruppa)This PR was submitted for the 4.3 branch but it was merged into the 4.4 branch instead (closes#35497).Discussion----------Fail on empty password verification (without warning on any implementation)| Q             | A| ------------- | ---| Branch?       | 4.4| Bug fix?      | sort of| New feature?  | no| Deprecations? | no| Tickets       || License       | MIT| Doc PR        |When using the sodium extension, an empty $raw string will issue a warning during validation, but the standard `password_verify()` does not. This PR aims to provide identical behavior independent of the underlying implementation. Two assumptions were made (please doublecheck if they are correct):- Empty password is never valid.- Empty password is not that severe that anybody needs to be informed using a warning or exception.Commits-------4d920f0 Fail on empty password verification (without warning on any implementation)
@fabpotfabpot merged commit4d920f0 intosymfony:4.4Feb 3, 2020
This was referencedFeb 29, 2020
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fabpotfabpotfabpot approved these changes

@nicolas-grekasnicolas-grekasnicolas-grekas approved these changes

@srozesrozeAwaiting requested review from sroze

Assignees

No one assigned

Projects

None yet

Milestone

4.4

Development

Successfully merging this pull request may close these issues.

5 participants

@umulmrum@nicolas-grekas@fabpot@javiereguiluz@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp