Bug 948165 - When choosing a weak password when creating the user in anaconda, a warning appears at the bottom “The password is weak, press the OK button twice to confirm”. But actually pressing the OK button once is enough
Summary: When choosing a weak password when creating the user in anaconda, a warning a...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 976236 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-04 08:20 UTC by Mike FABIAN
Modified: 2015-02-18 11:10 UTC (History)
9 users (show)

Fixed In Version: anaconda-20.1-1
Clone Of:
Environment:
Last Closed: 2015-02-18 11:10:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
password-weak-warning-says-to-press-OK-button-twice-but-pressing-once-is-enough.png (82.53 KB, image/png)
2013-04-04 08:20 UTC, Mike FABIAN
no flags Details

Description Mike FABIAN 2013-04-04 08:20:12 UTC
Created attachment 731470 [details]
password-weak-warning-says-to-press-OK-button-twice-but-pressing-once-is-enough.png

- Default install of Fedora-19-Alpha-TC4-x86_64-DVD.iso  (in qemu, should not mater)

- During the installation of the packages, when creating a user
  a warning appears when entering a weak password:

  “入力されたパスワードでは弱すぎす。確認する場合は完了を 2 回押す必要があります。”

  = “The password is week, press the OK button twice to confirm”.

  But actually pressing the OK button once is enough.

Comment 1 Vratislav Podzimek 2013-04-05 09:25:35 UTC
Can you please test it once more with something like "aaaa" as a password? I've just tried that and I had to click on Done twice to get back to the installation progress screen.

If you find some "magic value" that triggers this bug, please provide it. Otherwise I'll close this bug as WORKSFORME.

Comment 2 Mike FABIAN 2013-04-05 10:22:31 UTC
I cannot reproduce anymore  either with TC4.

Was anything fixed/changed there?

Comment 3 Vratislav Podzimek 2013-04-05 18:35:36 UTC
(In reply to comment #2)
> I cannot reproduce anymore  either with TC4.
> 
> Was anything fixed/changed there?
I'm not aware of any change. Maybe it was a some problem with virutalization that time?

Anyway, I'm closing this as WORKSFORME. If anybody can reproduce this, please reopen the bug and describe the reproducer.

Comment 4 Mike FABIAN 2013-04-08 11:12:12 UTC
I still can reproduce this on TC5, although not reliably.
I’ll reopen only if I find a reliable procedure to reproduce it.

Comment 5 Cybertimber2011 2013-05-01 14:39:02 UTC
I see this with Fedora-19-i686-Alpha iso in Virualbox 4.2.12.
Password was four lowercase letters followed by four numbers (e.g. pass1234) under User Creation, and the user was designated to be an administrator.

Comment 6 Mike FABIAN 2013-05-06 11:53:01 UTC
I also still see this from time to time, but it is now always
reproducible for me.

Comment 7 Vratislav Podzimek 2013-05-06 12:09:30 UTC
I've just tested (with rawhide anaconda, but no changes have been done in the code) and I still cannot reproduce this. Mike, are you using VirtualBox as well?

Comment 8 Mike FABIAN 2013-05-06 12:24:23 UTC
I am using qemu-kvm

Comment 9 Mike FABIAN 2013-05-06 12:25:01 UTC
(In reply to comment #6)
> I also still see this from time to time, but it is now always
> reproducible for me.

Sorry, I meant *not* always reproducible, only sometimes.

Comment 10 Jeff Bastian 2013-05-22 20:43:26 UTC
I can reproduce this every time by creating a user with a password of "a.B-1234"
This password meets most of the requirements since it has lower- and upper-case letters, symbols, and numbers, but it's still weak since it has a sequence of numbers.

The warning on the bottom says:
The password you have provided is weak. You will have to press Done twice to con
firm it.

I only hit Done once and it's happy.

Comment 11 Jeff Bastian 2013-05-22 20:44:49 UTC
And I just tested with Fedora 19 Beta RC2 with anaconda-19.28-1

Comment 12 Vratislav Podzimek 2013-05-23 12:26:40 UTC
(In reply to Jeff Bastian from comment #10)
> I can reproduce this every time by creating a user with a password of
> "a.B-1234"
This works, thanks a lot for this reproducer!

Comment 13 Vratislav Podzimek 2013-06-05 11:00:08 UTC
Patch posted to anaconda-patches, however I'm not sure it will make it to the f19-branch.

Comment 14 Fedora Update System 2013-06-06 18:37:13 UTC
anaconda-19.30.3-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/anaconda-19.30.3-1.fc19

Comment 15 Fedora Update System 2013-06-07 15:41:47 UTC
Package anaconda-19.30.3-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.30.3-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-10283/anaconda-19.30.3-1.fc19
then log in and leave karma (feedback).

Comment 16 Fedora Update System 2013-06-12 03:38:12 UTC
anaconda-19.30.3-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 17 Brian Lane 2013-06-21 01:14:22 UTC
*** Bug 976236 has been marked as a duplicate of this bug. ***

Comment 18 Brian Lane 2013-06-21 01:15:13 UTC
Still a problem with TC6 apparently.

Comment 19 Nix\ 2013-06-21 09:14:47 UTC
TC6 still problem. Root password, user works fine for me. LiveCD i686 TC6

Comment 20 Vratislav Podzimek 2013-06-25 13:25:00 UTC
(In reply to Brian C. Lane from comment #18)
> Still a problem with TC6 apparently.
The same problem but on a different screen. A patch for the root password spoke sent to anaconda-patches.

Comment 21 Nix\ 2013-06-26 06:41:51 UTC
Still the bug with Fedora 19 RC1 LiveCD. Root password one time "done", user password two times "done". The bug still for root password.

Comment 22 Vratislav Podzimek 2013-06-26 10:04:05 UTC
This bug is neither a final blocker nor a freeze exception and thus the patch will appear in the first F20's build of the Anaconda. If you want to test the change (with F19's Anaconda), append 'updates=http://vpodzime.fedorapeople.org/948165_updates.img' to the boot options.

Comment 23 Fedora End Of Life 2015-01-09 22:33:03 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 24 Fedora End Of Life 2015-02-18 11:10:53 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.