I think your just alittle confused.
There are two crypts basically, the crypt function, and the crypt hash.
The crypt hash has the 8 letter limit for the most part and is not
really used anymore.
when you specify {CRYPT}, dovecot just uses the crypt function, from
libc or libcrypt, and then
On Fri, May 7, 2010 at 15:11, Pascal Volk <
user+dove...@localhost.localdomain.org
> wrote:
> On 05/07/2010 08:16 PM Phil Howard wrote:
> > I've decided that having users supply cleartext passwords for me to
> encrypt
> > and encode is a bad idea, anyway. So maybe I won't need dovecotpw. The
> >
On Fri, May 7, 2010 at 15:11, Pascal Volk <
user+dove...@localhost.localdomain.org
> wrote:
> On 05/07/2010 08:16 PM Phil Howard wrote:
> > I've decided that having users supply cleartext passwords for me to
> encrypt
> > and encode is a bad idea, anyway. So maybe I won't need dovecotpw. The
> >
On 05/07/2010 08:16 PM Phil Howard wrote:
> I've decided that having users supply cleartext passwords for me to encrypt
> and encode is a bad idea, anyway. So maybe I won't need dovecotpw. The
> idea is that users supply an already-encrypted password. Most of the users
> can fetch their login pa
I've decided that having users supply cleartext passwords for me to encrypt
and encode is a bad idea, anyway. So maybe I won't need dovecotpw. The
idea is that users supply an already-encrypted password. Most of the users
can fetch their login password from /etc/shadow on their own computer.
Wi
