From owner-freebsd-questions@FreeBSD.ORG Tue Aug 13 14:45:57 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 004DE517 for ; Tue, 13 Aug 2013 14:45:56 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 78F442BA1 for ; Tue, 13 Aug 2013 14:45:56 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id fq13so5922201lab.11 for ; Tue, 13 Aug 2013 07:45:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=livn9cfZmNigd9xOtSPuwtlAYWVfgNmCpz+tVSsbbHo=; b=xx88j08N5vgT0O4MOM2Gwsi6r0BmNvZGS0xh5gvTMP9l0jQuOL+54fLsUISsq9ebKY 6Z0CdJ6lV79bPq+PIjUK8zy8lbRQmzkRNOVoyCk0s++W8rws1AiLLgzWdjHX8P+ALBt5 JhXAC/jvnNeVJL+HtryuPFmOEpZHAHVCw7HehjFONINXHhTvZ1qgc6+tdgl8ZD8gX34c yMaEDkQlWnYvn+RwL9Ad9V6qki6ABjsf1+55CPsUDOo7+CELQDnQcgJDdqGR+xKEUmKU Ygr3aKXLjUH0yY20QF7Aui8Tcj9iiXOSmwzMRLgVDsLijngY5UGglt0LcXY97k4pT026 GO8A== X-Received: by 10.152.8.51 with SMTP id o19mr1788473laa.42.1376405154407; Tue, 13 Aug 2013 07:45:54 -0700 (PDT) Received: from [192.168.1.128] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id i9sm14239769laa.3.2013.08.13.07.45.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 13 Aug 2013 07:45:53 -0700 (PDT) Message-ID: <520A46A0.5010506@gmail.com> Date: Tue, 13 Aug 2013 17:45:52 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130809 Thunderbird/17.0.8 MIME-Version: 1.0 To: "O. Hartmann" Subject: Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set References: <20130813163001.3194750f@telesto> In-Reply-To: <20130813163001.3194750f@telesto> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2013 14:45:57 -0000 13.08.2013 17:30, O. Hartmann wrote: > For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT > successfully. But by now, out of the blue, login as the database's > supervisor "pgsql" remotely isn't possible any more. > > The appropriate lines in pg_hba.conf are: > > local all pgsql md5 > hostssl all pgsql 0.0.0.0/0 md5 > > The funny thing is: when login locally without providing a password > (swap md5 to trust in the "local" line) and setting the password for > the role "pgsql" via > > ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; I guess ENCRYPTED means you are substituting FooMe with md5 hashed password correctly salted with role name as postgresql requires? > or doing the same via pgadmin3 from remotely by also swapping md5 to > trust in the line "hostssl" for global network, it seems I could > alter/change the password for the supervisor pgsql. But restoring the > password check by setting back "md5" leaves me locked out! > > By the way, this strange behaviour occurs on ALL(!) PostgreSQL 9.2 > servers running on FreeBSD 10.0-CURRENT boxes. > > Ports databases/postgresql-XXX as well as FreeBSD is as of the latest > sources and up to date. > > What is going wrong? -- Sphinx of black quartz, judge my vow.