Remove "strong" password requirements

Bug #821727 reported by Richard Eames
54
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Canonical SSO provider
Fix Released
High
Unassigned
ubuntuone-control-panel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Please remove the requirement to have an uppercase character and a number for the password to sign up for Ubuntu One. This requirement stops me from being able to use my normal password scheme which are usually >15 characters and contain numerous symbols.
For example, some of my passwords are code fragments: "<?= $my_password->is_strong() == true; ?>"
Somehow I don't think that will get broken any time soon, and it has no digits or upper case.

And if a user wants to use an insecure password, that's their decision not Canonical's.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: ubuntuone-control-panel 1.0.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Fri Aug 5 16:54:11 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntuone-control-panel
UpgradeStatus: Upgraded to natty on 2011-04-29 (98 days ago)

Revision history for this message
Richard Eames (naddiseo) wrote :
dobey (dobey)
Changed in ubuntuone-control-panel (Ubuntu):
status: New → Invalid
Revision history for this message
Stuart Metcalfe (stuartmetcalfe) wrote :

We'd like to remove the *requirement* for a strong password and instead make it *recommended* with a password strength meter and accompanying advice about how to make it stronger if it's weak.

summary: - Remove "strong" password requirements for ubuntuone
+ Remove "strong" password requirements
Revision history for this message
Stuart Metcalfe (stuartmetcalfe) wrote :

We should have a minimum password length still, I think

Changed in canonical-identity-provider:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Stuart Metcalfe (stuartmetcalfe) wrote :

Marking as 'High' priority as user testing shows this is a major problem in the sign-up process.

Revision history for this message
Mike Coleman (tutufan) wrote :

My bug (885684) got merged into this one even though it's not quite the same thing.

Specifically, I don't have a problem with requiring strong passwords, as long as the requirement is that they be strong in terms of bits of information, and that the user is allowed to meet this requirement as they please. What I think is bad is requiring a certain pattern (8 chars, one uppercase, one digit, etc.) as a half-baked attempt to force the password to contain more information.

Revision history for this message
jablko (ms419) wrote :

I couldn't register with my 27 character password, which contained symbols. I don't have a problem with enforcing some minimum password strength, but I think the current determination of password strength is naive: http://xkcd.com/936/

tags: added: buy-software
tags: added: buying-software
removed: buy-software
Revision history for this message
smurfzilla (jhughesjr) wrote :

Have to agree with @Stuart - I actually did not create an account because of the password requirements.
If it get's resolved I'll switch over to using ubuntu one.

Revision history for this message
Joey Stanford (joey) wrote :

Howdy, please note that this bug's request cannot be applied to ~canonical and Canonical employees. Should there be a question about this, please contact me directly.

Revision history for this message
Daniel Manrique (roadmr) wrote :

OK, the existing validation code is less strict (@joey *except* for canonical employees who have stricter requirements). Essentially:

        Validation is successful if:
            - password contains at least 8 characters
            - password contains only ascii characters

This has been the case since 2012-12-19, it's just that the report had remained open since then.

I don't think requiring at least 8 chars is unreasonable, and that's currently the only "attempt" to force the password to contain more information". I think this solves the initial request so I'll close this report.

Changed in canonical-identity-provider:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.