Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id B3C7CB5DC00 for ; Wed, 19 Oct 2011 16:04:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 78009-02 for ; Wed, 19 Oct 2011 19:04:26 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from nm7.bullet.mail.bf1.yahoo.com (nm7.bullet.mail.bf1.yahoo.com [98.139.212.166]) by mail.postgresql.org (Postfix) with SMTP id 8C338B5DBFB for ; Wed, 19 Oct 2011 16:04:26 -0300 (ADT) Received: from [98.139.212.148] by nm7.bullet.mail.bf1.yahoo.com with NNFMP; 19 Oct 2011 19:04:26 -0000 Received: from [98.139.212.206] by tm5.bullet.mail.bf1.yahoo.com with NNFMP; 19 Oct 2011 19:04:26 -0000 Received: from [127.0.0.1] by omp1015.mail.bf1.yahoo.com with NNFMP; 19 Oct 2011 19:04:26 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 144836.6505.bm@omp1015.mail.bf1.yahoo.com Received: (qmail 63968 invoked by uid 60001); 19 Oct 2011 19:04:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1319051065; bh=Ga5KEyPJGe7Wr99CyYD2PQ26LF7ZD2JQcXz9bRFmKWI=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=yv+9SvHcydmbphSvoj6VQ1BRh5jMm3NR+kUdEzykKvGXaWCx0FpSNQXmai3R9lnz8JsNXq5XuPujHeGxi7iUo4YxVv6b0/NGS99To7bAI/hRtDb7OQM7lgj2ycmrMUm52PIHC8R5Z799pwS2t+QGYpRzs0q9t+4Q8SUdvpK5WIY= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=AorHXaUXUbMUBUNqOUxmsFY4ShNx8dBl8fXtCj32KzDVk5/2ovRp0PLj9c4AtPf4mmn5aHS1cSt3QGYbObghkYM5xp+Ax77dKp8Z6GdzpkyMJBk+jv+91uhSdpa0qrdiunS/HZiTexwKa7Y/7RHjN14WdpmEmGV7e/WfL8BrzOI=; X-YMail-OSG: Mkk9pggVM1m1OG3XkpVfiCcE75ygeyHxklgGfUjsQQ5tctZ dF.ETbIBawfxpO.DplxjtxyNkOoGG.UdAJcyNXKmPWCd9LpD7ZXbeLM5cp7l AHB2FXXlC.YwpVkWtcLlo4k9vYGS0St42fNTirp8d39oDiR9Yz45EmQV7k6_ BS1WDUo3IVUk3unKahWYc4Usnen9KnOhV6IPeTt4NzCohfiidE9UAOP_rVKk Xlh9fKxBZ1uK43oqLATm696Sh29.uGHuH8b2savT87axsZ_W_yMIBSGFhnaW D7WB5iFof_JW3EZ9MtfAq5e6YcF2t2r09N.ugQoPxiOjXRjKLT4I7WUPy2zF iiRCcozrrMnBS2h9kNCbuYuKereZBTkcT_wGqJ4NUZBjZC1VFmTKEZCZmNHF Msb38UhfH5zvIv9z30HcwM1inXppHTv6Dg_nHOAq1ahYX..ul3dpzyZ_0qbt O1Cr3p9v3SfPwZiVSxo9c1WwYZxCQdoeccO6.we4mstEQYCuoTc.W_OVTBgZ 4p8CnY_Vw.5uhTxJwOUFxQ_Apk6ObjHJwhYLRO6LdambTWQ-- Received: from [66.201.46.98] by web160714.mail.bf1.yahoo.com via HTTP; Wed, 19 Oct 2011 12:04:25 PDT X-Mailer: YahooMailWebService/0.8.114.317681 Message-ID: <1319051065.63555.YahooMailNeo@web160714.mail.bf1.yahoo.com> Date: Wed, 19 Oct 2011 12:04:25 -0700 (PDT) From: Fred Cox Reply-To: Fred Cox Subject: Algorithm for generating md5 encrypted password not found in documentation To: "pgsql-docs@postgresql.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-1817860329-1413844745-1319051065=:63555" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.421 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.504 X-Spam-Level: X-Archive-Number: 201110/60 X-Sequence-Number: 7060 ---1817860329-1413844745-1319051065=:63555 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On=A0http://www.postgresql.org/docs/9.1/interactive/sql-createrole.html the= re is mention of a possibility of setting a password for a new role by supp= lying it in md5 format. =A0This format doesn't seem to be documented.=0A=0A= "If the presented password string is already in MD5-encrypted format, then = it is stored encrypted as-is"=0A=0ALooking at pg_dumpall let me know that t= he string needs to start with "md5" but a naive running if my password thro= ugh the command line md5 utility and prefixing "md5" was not correct.=0A=0A= If the algorithm is documented elsewhere, can it be linked from this page?= =0A=0AThanks,=0A=0AFred ---1817860329-1413844745-1319051065=:63555 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
On&nb= sp;http://www.postgresql.org/docs/9.1/interactive/sql-createrole.html there= is mention of a possibility of setting a password for a new role by supply= ing it in md5 format.  This format doesn't seem to be documented.

"If the presented password string is already in MD5-encrypted format= , then it is stored encrypted as-is"

Looking at pg_dumpal= l let me know that the string needs to start with "md5" but a naive running= if my password through the command line md5 utility and prefixing "md5" wa= s not correct.

If the al= gorithm is documented elsewhere, can it be linked from this page?

Thanks,

Fred
---1817860329-1413844745-1319051065=:63555--