Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jun 2013 17:49:56 +0330
From:      takCoder <tak.official@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD maximum password length
Message-ID:  <CAPkyVLwNAUU_2E0d8Go6OP4m7jqHeHKCWEt5WRhtYcgRBSQ2nQ@mail.gmail.com>
In-Reply-To: <44li69diyv.fsf@be-well.ilk.org>
References:  <CAPkyVLw=m5-3HX7YC-Zqm=OgTLMhNYq4trBSWso8qEmPzqV38Q@mail.gmail.com> <44li69diyv.fsf@be-well.ilk.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, Lowell, for your reply. :)
>> And i've heard that no-maximum-limits for passwords length is only
possible
>> when we keep them in encrypted form not as plain text, which i think is
>> matched with FreeBSD behavior.
>
>Is plain-text passwords even a supported behaviour? I didn't think it was.
>

> I meant i think FreeBSD does not use plain-text passwords, so we won't
have a limitation for that reason.. excuse me for my poor english.

>_PASSWORD_LEN is the defined limit. It's 128 characters by default but
>could be changed at compile time. There may be other limits, such as in
>various versions of NIS.
...
>I'm not sure I understand what you're doing, so I don't have any real
>advice, but I don't see why 128 characters would be that hard to deal
>with.

I need to moderate the input password in my system's user interface. And I
believe i have tested longer passwords than that, about 1000 characters
long, and there was no limitations, via using this command in a /bin/sh
test shell script : "echo PASSWORD | pw user mod USER -h 0".

at least there was no errors reported by *pw*. i did not test the user
myself.. and it somehow seems correct, as the encrypted output string may
be not a function of the input string, based on the method used.

Thank you :)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPkyVLwNAUU_2E0d8Go6OP4m7jqHeHKCWEt5WRhtYcgRBSQ2nQ>