[wp-hackers] 'Password Protected' - bug or feature?

[Shashi]

but straight whitespaces? only [\w]+ being the password sux man!

On Tue, Dec 9, 2008 at 7:11 PM, Matt Martz <matt at sivel.net> wrote:
> On Tue, Dec 9, 2008 at 6:06 AM, Shashi <connect2shashi at gmail.com> wrote:
>> I think so too...
>>
>> On Tue, Dec 9, 2008 at 4:07 PM, Rich Pedley <elflop at googlemail.com> wrote:
>>> Just had this problem from a user. They apparently entered a space
>>> into the password field, but hadn't realised they had done so. They
>>> couldn't then figure out why their post came up as password protected.
>>>
>>> Shouldn't it be 'trimmed'  to remove spaces?
>
> I am not sure if it should.  People are starting to be trained to use
> pass phrases instead of pass words.  Pass phrases could include
> spaces, and I have indeed seen users place spaces before and after
> because they think it makes it harder to guess.  Perhaps adding a
> password length counter would be beneficial so that you could see the
> total number of characters entered.
>
> --
> Matt Martz
> matt at sivel.net
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
    ,               ,
   /                 \
  ((__-^^-,-^^-__))
   `_----' `-----_-'
   `--|  o`   'o |--'
       \  `      /
        ):    : (
        :o__o:
         "---- "

   www.gnu.org
www.uncorkers.org