[wp-trac] [WordPress Trac] #881: Lengthen password field for protected posts
WordPress Trac
noreply at wordpress.org
Mon Oct 26 18:26:37 UTC 2015
#881: Lengthen password field for protected posts
--------------------------+-----------------------------
Reporter: ScytheBlade1 | Owner: pento
Type: enhancement | Status: assigned
Priority: normal | Milestone: Future Release
Component: Database | Version:
Severity: normal | Resolution:
Keywords: needs-patch | Focuses:
--------------------------+-----------------------------
Changes (by DrewAPicture):
* keywords: has-patch dev-feedback => needs-patch
* component: Security => Database
Comment:
Replying to [comment:23 chriscct7]:
> While this might involved a database change (possibly, depending on what
approach is taken), I think this issue would be best served in the
security component (as it deals explicitly with password storage), at
least until the issue is for-sure going to require a database change.
I'm gonna have to go ahead and sort of disagree with you there. I think
this is a database issue and we should realistically lengthen the field
and inputs to 191 characters and walk away.
Plus, the field is already filterable via the field filters in
`sanitize_post_field()`.
Per the hashing suggestion, I don't think we need to go there –
specifically because I think people are going set passwords and will
expect to be able to retrieve them later, which hashing would nix.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/881#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list