From: Brian Mathis <brian.mathis@gmail.com>
To: Marko Kreen <markokr@gmail.com>
Cc: Tino Wildenhain <tino@wildenhain.de>
Cc: Ranieri Mazili <ranieri.oliveira@terra.com.br>
Cc: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: Encrypted column
Date: Tue, 5 Jun 2007 11:22:04 -0400
Message-ID: <183c528b0706050822t64a067aeg74d4190ae2a51807@mail.gmail.com> (raw)
In-Reply-To: <e51f66da0706050809r3da6c61eqf8e6f73ae8a1cc82@mail.gmail.com>
References: <46645B01.6070605@terra.com.br>
<4665161F.9090009@wildenhain.de>
<e51f66da0706050712u3c59a369n986ae56344912a24@mail.gmail.com>
<183c528b0706050726v3214820fx6669d1e99bcfaaa@mail.gmail.com>
<e51f66da0706050739v4d504853va2d3f60719690da@mail.gmail.com>
<e51f66da0706050809r3da6c61eqf8e6f73ae8a1cc82@mail.gmail.com>
On 6/5/07, Marko Kreen <markokr@gmail.com> wrote:
> On 6/5/07, Marko Kreen <markokr@gmail.com> wrote:
> > both md5 and sha1 are actually easier to bruteforce than
> > the old DES-based crypt.
>
> If this statement seems weird - the problem is the speed.
> MD5 and SHA1 are just faster algorithms than des-crypt.
>
> And there's nothing wrong with fast general-purpose algorithms,
> as long their cryptographic properties hold. Starting from
> 20-30 bytes the bruteforce is really not an option.
>
> But if you have under 10 bytes (let be honest - you have
> 6 bytes...) the speed start to matter, because it is possible
> on random laptop to simply try all combinations.
>
> --
> marko
>
pgcrypto also supports md5, so I'm not sure what you're referring to
here. As I already mentioned, *salting* before you hash is a very
important step. I'm not sure if you saw that in my post. Without a
salt, it's trivial to generate a list of all combinations of md5'd
strings and their results, up to reasonable lengths. Then it would be
very simple to look up each hash and get the original text. With a
salt, you need to generate all possible md5s for all possible salts --
a much harder task.
In any case, pgcrypto seems to be a nice and full featured tool, so
one should use that instead of rolling their own.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: brian.mathis@gmail.com, markokr@gmail.com, tino@wildenhain.de, ranieri.oliveira@terra.com.br, pgsql-general@postgresql.org
Subject: Re: Encrypted column
In-Reply-To: <183c528b0706050822t64a067aeg74d4190ae2a51807@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox