X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CD70ED6854 for ; Wed, 2 Nov 2005 05:26:32 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57589-02 for ; Wed, 2 Nov 2005 09:26:29 +0000 (GMT) Received: from pjetlic.mobart.hr (pjetlic.mobart.hr [80.80.51.10]) by svr1.postgresql.org (Postfix) with ESMTP id 460B0D6819 for ; Wed, 2 Nov 2005 05:26:30 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by pjetlic.mobart.hr (Postfix) with ESMTP id 4407E17A0E for ; Wed, 2 Nov 2005 10:26:27 +0100 (CET) Received: from pjetlic.mobart.hr ([127.0.0.1]) by localhost (pjetlic [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27266-01-2 for ; Wed, 2 Nov 2005 10:26:27 +0100 (CET) Received: from mike.mobart.hr (mike.mobart.hr [192.168.10.94]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pjetlic.mobart.hr (Postfix) with ESMTP id 2943517449 for ; Wed, 2 Nov 2005 10:26:27 +0100 (CET) Subject: Re: PGSQL encryption functions From: Mario Splivalo Reply-To: mario.splivalo@mobart.hr To: pgsql-sql@postgresql.org In-Reply-To: <28738.1130883210@sss.pgh.pa.us> References: <200511011438.06610.mark.dingee@cox.net> <20051101212844.GA24861@wolff.to> <200511011700.50776.mark.dingee@cox.net> <28738.1130883210@sss.pgh.pa.us> Content-Type: text/plain Organization: Mob-Art Date: Wed, 02 Nov 2005 10:26:27 +0100 Message-Id: <1130923587.7739.11.camel@ekim> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by OpenSource AV+AS Mail Server X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.003 required=5 tests=[AWL=0.003] X-Spam-Score: 0.003 X-Spam-Level: X-Archive-Number: 200511/19 X-Sequence-Number: 23271 On Tue, 2005-11-01 at 17:13 -0500, Tom Lane wrote: > "Mark R. Dingee" writes: > > md5 works, but I've been able to > > brute-force crack it very quickly, > > Really? Where's your publication of this remarkable breakthrough? I'd say you can't bruteforce md5, unless you're extremley lucky. However, md5 is easily broken, you just need to know how to construct the hashes. One could switch to SHA for 'increaased' security. Although I don't think he'd be having problems using MD5 as he described it. I'd also lilke to see he's example of brute-force 'cracking' the MD5 digest. Mike -- Mario Splivalo Mob-Art mario.splivalo@mobart.hr "I can do it quick, I can do it cheap, I can do it well. Pick any two."