#779 closed enhancement (wontfix)
proposal for user selected password during registration
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.1 |
| Component: | Registration | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
bbPress should enhance the registration process to the modern friendly method of allowing the user to create their own password rather than an initial harsh random one that is hard to remember/copy.
This improvement would have an important benefit of not sending real passwords via email in clear text and archived in their email accounts for hackers to find.
method:
two mandatory additional fields on the register.php page, one for the password, a second to verify since it will be hidden as they type, ala *
optionally, some simple javascript processing could be added to alert the user to the password strength
the currently generated random password can be used instead in an email, still sent and required to be checked, as an authorization code to prove ownership of an email account
ie.
"please click this link to activate your account http://bbpress.org/forums/?account-verify=583%$#1*"
This auth code would have to be stored in user meta data, kept as md5/hash etc. like the current password method uses, so a hacker cannot take advantage of un-activated accounts if they get ahold of the db.
The accounts would have to start on inactive status and be upgraded to active, deleting the auth code after activation to prevent re-use.
A user who forgets their password would be sent a new auth code, instead of a replacement password - then upon verifying with the link, they would get taken to a page to enter a new password for themselves.
Change History (9)
- Milestone changed from 0.9 to 1.0-beta & XML-RPC
- Version set to 1.0-alpha (trunk)
comment:4
nightgunner5 — 4 years ago
This should be an option, defaulting to user-selected passwords on new installs and random passwords on preexisting bbPress installations.
Storing the activation key in a hash does not prevent a hacker with access to the database from doing anything. They can simply remove the key from accounts they wish to activate.
I think the verification should be a random 16 character string of capital letters, lowercase letters, numbers and a few symbols that aren't "special" for URLs (% and & are out of the question).
The main problem would be that this would either add a few queries on each login or change the bb_users table schema (which is connected to WordPress/BackPress?, so probably the first option).
- Milestone changed from 1.0 to 1.5
I still want to see this happen, but not for 1.0
comment:8
johnjamesjacoby — 2 years ago
- Resolution set to wontfix
- Status changed from new to closed
The bbPress plugin will reap the benefits of other WordPress plugins that handle this. Closing as wontfix.
- Milestone changed from Future Release to 1.1
- Version 1.0-rc-2 deleted
I'm open to this, but it needs to go back to 1.0-beta I think.
We should discuss approaches to this here though.