Em 31/07/2010 18:51, Patrick Westenberg escreveu:
Leonardo Rodrigues schrieb:
that's all because i already have a account manager system,
written on PHP, which i had to kept. So i was trying to understand
how that's work to make it work on my system i couldnt stop using.
but after s
On 15.2.2010, at 19.42, Leonardo Rodrigues wrote:
>from sources on src/auth i can find some interesting informations:
>
> /* format: */
>
> and
>
> #define SSHA256_SALT_LEN 4
>
> so the salt really seems to be 4-byte (which in fact are 8 when watching in
> hexadecimal), the exact differe
that's all because i already have a account manager system, written
on PHP, which i had to kept. So i was trying to understand how that's
work to make it work on my system i couldnt stop using.
but after some tryings i got everything running. All my passwords
were already migrated fr
Why not make it easy on yourself. Just let dovecot use crypt, and use
whatever format your system crypt supports.
Personally I'm using 16byte salt, sha512 for mine this way. Seems
should work with everything, that lets you use the system's crypt.
Quoting Leonardo Rodrigues :
Em 14/02/2010
Em 14/02/2010 04:53, to...@tuxteam.de escreveu:
No, just let Dovecot's algorithm do the generation (and later checking)
of the password? (I might be misunderstanding your problem, though).
unfortunelly i cant do that. I have my own accounts admin system,
written in PHP, which does ma
Leonardo Rodrigues wrote:
The idea of salted hash algorithms is to generate a different hash
even if the same text is entered. That can be easily seen with dovecotpw:
using NON-salted SHA256, same hash is generated for a given password
[r...@correio ~]# dovecotpw -s SHA256 -p 123
{SHA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Feb 13, 2010 at 10:09:34PM -0200, Leonardo Rodrigues wrote:
>
> The idea of salted hash algorithms is to generate a different hash even
> if the same text is entered. That can be easily seen with dovecotpw:
I don't know about dovecot's al
The idea of salted hash algorithms is to generate a different hash
even if the same text is entered. That can be easily seen with dovecotpw:
using NON-salted SHA256, same hash is generated for a given password
[r...@correio ~]# dovecotpw -s SHA256 -p 123
{SHA256}pmWkWSBCL51Bfkhn79xPu
