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 15A0FD776B for ; Wed, 2 Nov 2005 10:04:03 -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 61986-01 for ; Wed, 2 Nov 2005 14:03:59 +0000 (GMT) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by svr1.postgresql.org (Postfix) with ESMTP id 82764D7070 for ; Wed, 2 Nov 2005 10:04:01 -0400 (AST) Received: by xproxy.gmail.com with SMTP id t6so208797wxc for ; Wed, 02 Nov 2005 06:04:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JwGyhh1G4VYUQF2szOiOm4WocYQNYlvleZXKwofrMYLjP186fpMIxxzQPKKr6TV29b2MEsW1eaOjTupneffUTD5P+PH7qmNSXFRu6aZZNagL42rSzW2DvXey3v39+WGTnw2SwrIA0XMHQmSkzTN5ERIl2YQLQo+6PzlM/kQ5R34= Received: by 10.70.44.3 with SMTP id r3mr1223152wxr; Wed, 02 Nov 2005 06:04:05 -0800 (PST) Received: by 10.70.51.8 with HTTP; Wed, 2 Nov 2005 06:04:05 -0800 (PST) Message-ID: Date: Wed, 2 Nov 2005 14:04:05 +0000 From: Neil Saunders To: "Mark R. Dingee" Subject: Re: PGSQL encryption functions Cc: pgsql-sql@postgresql.org, mario.splivalo@mobart.hr In-Reply-To: <200511020829.48299.mark.dingee@cox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200511011438.06610.mark.dingee@cox.net> <28738.1130883210@sss.pgh.pa.us> <1130923587.7739.11.camel@ekim> <200511020829.48299.mark.dingee@cox.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.861 required=5 tests=[AWL=-0.471, RCVD_IN_BL_SPAMCOP_NET=1.332] X-Spam-Score: 0.861 X-Spam-Level: X-Archive-Number: 200511/25 X-Sequence-Number: 23277 OK, you're not really "breaking" md5. If the attacker already knows the information being encrypted, then all you're testing is the concatenation order- Surely the information is more important than the order? md5 is a one way hash function, and so using an alternate algorithm will provide no benefit whatsoever; you're just running through 9 permutations. Kind Regards, Neil. On 11/2/05, Mark R. Dingee wrote: > Mike & Tom, > > The script I'm using to "break" md5 presumes that the cracker knows the 3 > elements being concatenated together to form the plain-text sting which i= s > then passed into md5. The method I'm using then begins running through > various permutations. Do you believe that the methodology is appropriate= or > that I'm being a bit paranoid? > > Thanks > > On Tuesday 01 November 2005 05:13 pm, 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? > > > > regards, tom lane > > > > ---------------------------(end of broadcast)--------------------------= - > > TIP 1: if posting/reading through Usenet, please send an appropriate > > subscribe-nomail command to majordomo@postgresql.org so that you= r > > message can get through to the mailing list cleanly > > On Wednesday 02 November 2005 04:26 am, Mario Splivalo wrote: > > 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 describe= d > > it. I'd also lilke to see he's example of brute-force 'cracking' the MD= 5 > > digest. > > > > Mike > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >