Ticket #881 (closed enhancement: wontfix)

Opened 7 years ago

Last modified 5 years ago

Lengthen password field for protected posts

Reported by: ScytheBlade1 Owned by: Nazgul
Priority: normal Milestone:
Component: Optimization Version:
Severity: normal Keywords: has-patch commit
Cc: ScytheBlade1

Description

You know, if you lengthen the database column size to 32 and then just md5() it, users essentially would have unlimited password length for a post. However, since I take it that the ability to actually see the password that you input is enjoyed in wordpress, increasing the max length to 50 or so would be greatly appreciated.

It's just that 20 is so short...

Attachments

patch Download (969 bytes) - added by ScytheBlade1 7 years ago.
881.patch Download (629 bytes) - added by skippy 6 years ago.
881b.diff Download (693 bytes) - added by Nazgul 5 years ago.

Change History

  • Patch set to No

Actually, a possible idea as to implimentation:

1) On the side of the password area, add a checkbox labeled "Encrypt Password". Make it a link to documentation explaining: -That by checking this box, you have no way of obtaining your password again, less resetting it -This also allows you to enter passwords much greater than 20 in length When this box is checked, and you're editing the post, the password box should display "[Encrypted]". When the form is submitted, if that field has changed at all from that string, simply update the password. 2) Just the same, make it at least 50 for plaintext. I tend to use phrases instead of passwords, that go along with the post title.

I made the change locally in my database (to raise the limit to 50), it really is a "why not" thing. The encryption option is only an added bonus that's easily implimented alongside it.

  • Keywords patch removed

skippy6 years ago

  • Keywords bg|has-patch bg|commit bg|squashed added
  • Owner changed from anonymous to skippy
  • Status changed from new to assigned
  • Component changed from General to Optimization

added 881.patch, svn diff against wp 1.6 snapshot. dbdelta should roll this out in upgrade.php

  • Milestone set to 2.1

Nazgul5 years ago

  • Keywords has-patch commit added; bg|has-patch bg|commit bg|squashed removed
  • Owner changed from skippy to Nazgul
  • Status changed from assigned to new

I refreshed the patch. It's now in par with the password length for users. It doesn't seem logical to have different maximum password lengths for both.

As this ticket has been sleeping for some time I'd let the encryption part slide. If somebody wants that, they can open a new ticket and code it.

comment:7   matt5 years ago

  • Status changed from new to closed
  • Resolution set to wontfix
  • Milestone 2.1 deleted
Note: See TracTickets for help on using tickets.