From MichaelDBA@sqlexec.com Tue Oct  30 17:51:57 2018
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gHYBY-0006Ac-6K
	for pgsql-performance@arkaria.postgresql.org; Tue, 30 Oct 2018 17:52:12 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gHYBW-0008Ix-2y
	for pgsql-performance@arkaria.postgresql.org; Tue, 30 Oct 2018 17:52:10 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <MichaelDBA@sqlexec.com>)
	id 1gHYBV-0008Iq-RP
	for pgsql-performance@lists.postgresql.org; Tue, 30 Oct 2018 17:52:09 +0000
Received: from mout.perfora.net ([74.208.4.197])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <MichaelDBA@sqlexec.com>)
	id 1gHYBP-00065b-8L
	for pgsql-performance@lists.postgresql.org; Tue, 30 Oct 2018 17:52:09 +0000
Received: from [192.168.1.101] ([98.169.208.73]) by mrelay.perfora.net
 (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0M88Ot-1fMXon0goD-00vfdd
 for <pgsql-performance@lists.postgresql.org>; Tue, 30 Oct 2018 18:52:00 +0100
Received: from [192.168.1.101] ([98.169.208.73]) by mrelay.perfora.net
 (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0M88Ot-1fMXon0goD-00vfdd
 for <pgsql-performance@lists.postgresql.org>; Tue, 30 Oct 2018 18:52:00 +0100
Message-ID: <5BD89A3D.5060108@sqlexec.com>
Date: Tue, 30 Oct 2018 13:51:57 -0400
From: MichaelDBA <MichaelDBA@sqlexec.com>
User-Agent: Postbox 5.0.25 (Windows/20180328)
MIME-Version: 1.0
To: pgsql-performance@lists.postgresql.org
Subject: SCRAM question
Content-Type: multipart/alternative;
 boundary="------------070905070800060901060306"
X-Provags-ID: V03:K1:RTp82ffMMk2OOOMlat1WvMCSXWl5NK9BeqRQz/q0LPCt0nBmzeb
 HHxtNLPBcBOOJEsXrAs94TifDNS+dHL54m38+MeVdIVGN/WS7MJ+kx21W6iE1LSIfVntNDT
 ArkycBE+PDY8Hcrya34uRZuOrgyBqBT9IAQfzZkMJIZqaAajiCxoqnsk0z5eY7gsJf6THMA
 3igHn73LLycpVQrEjqOyA==
X-Spam-Flag: NO
X-UI-Out-Filterresults: notjunk:1;V01:K0:0ZblIcLXwzg=:IRZpJ/5zGslALw8u2s/EzL
 W4VJNfTzk06oEJ4NqbbQSr1ia86Do4rXmpTNAIQvqqAWDxHsfVFTp/mCeyVNJ+ZPdlnJQRU1C
 lj6ohgdzhGCAOodzYdXTPpWL0Et2ltizBcVdz0Tu12BI1tzywFqdoxYRo6swTOv8a5tkePEhX
 cXNXAYvQ1/dsDY0nq1rjLhp0bVRKt/ci/Yz9PXy7sYjKf6RuGpfv5Q/ZUgh2Tyx9kaKlh+B3N
 Ep/G6QsLa+296kXRcfUChEHFRSJ1EV9cd6QEJcA96GOnN9JYzznA0m1LwqRazk8alDt97hDoy
 hQF2jKbjPp7n6JGpNIuYVK3IyPunnusOn+PD3K+OWlAzDk1AaGgV1Kps0RKO4Y0P2kgYPUnZz
 NYYOYbpsGHStgo+/LNuZx0Ce7CQEuIJqwaB9J6fkskcC9WFFPPW9tw/B9XNQ0s6+0pPdwTXZh
 ggRfTKFdXgtY1J8AUCTlKFridxijlwTSHMK7Gn9uyzqS7waze694yeZ75BmnWZxBtAgGUZfkY
 uo5Ul9yqDlTRrVZwYofT8/ynS+vvIE9ZgIcYBiLQpUzLKXg/y5TdJUDnzt49VHUDGseW7FrCQ
 QZCXkLnJs69s8CHwcVZztrPvx4Oo/7yICUgKeTXM35OgCIKRc5KOUQj8Braj0E0j0Q67nTsTK
 bCus4rzejgug9wOJtzLAVsPSj/cFRcGKIcG2YfU+g3+TccNloB2cXFgNZGaVCM7El+H1Qwjyp
 DJjY32OjYM12uRID
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

This is a multi-part message in MIME format.
--------------070905070800060901060306
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I am using pgadmin4 version 3.4 with PG 11.0 and I get this error when I 
try to connect with scram authorization:

User "myuser" does not have a valid SCRAM verifier.

How do I get around this?   And also how would I do this for psql?

Regards,
Michael Vitale

--------------070905070800060901060306
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"></head><body
 bgcolor="#FFFFFF" text="#000000">
I am using pgadmin4 version <span 
__postbox-detected-content="__postbox-detected-date" 
class="__postbox-detected-content __postbox-detected-date" 
style="display: inline; font-size: inherit; padding: 0pt;">3.4</span> 
with PG <span __postbox-detected-content="__postbox-detected-date" 
class="__postbox-detected-content __postbox-detected-date" 
style="display: inline; font-size: inherit; padding: 0pt;">11.0</span> 
and I get this error when I 
try to connect with scram authorization:
  <br>

  <br>
User "myuser" does not have a valid SCRAM verifier.
  <br>

  <br>
How do I get around this?  
And also how would I do this for psql?<br>

  <br>
Regards,
  <br>
Michael Vitale
</body>
</html>

--------------070905070800060901060306--




From jd@commandprompt.com Tue Oct  30 18:03:14 2018
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gHYMR-0006iK-Ho
	for pgsql-performance@arkaria.postgresql.org; Tue, 30 Oct 2018 18:03:27 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gHYMP-0000cd-JC
	for pgsql-performance@arkaria.postgresql.org; Tue, 30 Oct 2018 18:03:25 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <jd@commandprompt.com>)
	id 1gHYMP-0000c8-83
	for pgsql-performance@lists.postgresql.org; Tue, 30 Oct 2018 18:03:25 +0000
Received: from lists.commandprompt.com ([2604:da00:2:2:5054:ff:fe07:7618])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <jd@commandprompt.com>)
	id 1gHYMM-0006Nl-2V
	for pgsql-performance@lists.postgresql.org; Tue, 30 Oct 2018 18:03:23 +0000
Received: from [192.168.50.9] (spinlock.commandprompt.com [69.168.55.30])
	by lists.commandprompt.com (Postfix) with ESMTPA id AB3A37C7;
	Tue, 30 Oct 2018 11:03:15 -0700 (PDT)
Received: from c-73-97-49-9.hsd1.wa.comcast.net ([73.97.49.9]
	helo=[192.168.50.9]) by assp.commandprompt.com with SMTPSA(TLSv1_2
 ECDHE-RSA-AES128-GCM-SHA256) (2.5.1);
	30 Oct 2018 11:03:15 -0700
Subject: Re: SCRAM question
To: MichaelDBA <MichaelDBA@sqlexec.com>,
 pgsql-performance@lists.postgresql.org
References: <5BD89A3D.5060108@sqlexec.com>
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
Message-ID: <7460ee84-6c64-dcbc-4fc6-c88507ccb2ee@commandprompt.com>
Date: Tue, 30 Oct 2018 11:03:14 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <5BD89A3D.5060108@sqlexec.com>
Content-Type: multipart/alternative;
 boundary="------------3DC31E156D92D6B76F5D1DCC"
Content-Language: en-US
X-Assp-Version: 2.5.1(16177) on assp.commandprompt.com
X-Assp-ID: assp.commandprompt.com m1-22595-10288
X-Assp-Session: 7F56E8634600 (mail 1)
X-Assp-Original-Subject: Re: SCRAM question
X-Assp-Client-SSL: yes
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

This is a multi-part message in MIME format.
--------------3DC31E156D92D6B76F5D1DCC
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 10/30/18 10:51 AM, MichaelDBA wrote:
> I am using pgadmin4 version 3.4 with PG 11.0 and I get this error when 
> I try to connect with scram authorization:
>
> User "myuser" does not have a valid SCRAM verifier.
>
> How do I get around this? And also how would I do this for psql?

You need to update the password using SCRAM I believe...

|See here: 
https://paquier.xyz/postgresql-2/postgres-10-scram-authentication/|

|
|

|JD
|

>
> Regards,
> Michael Vitale 


-- 
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
***  A fault and talent of mine is to tell it exactly how it is.  ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
*****     Unless otherwise stated, opinions are my own.   *****


--------------3DC31E156D92D6B76F5D1DCC
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 10/30/18 10:51 AM, MichaelDBA wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:5BD89A3D.5060108@sqlexec.com">
      <meta http-equiv="content-type" content="text/html;
        charset=windows-1252">
      I am using pgadmin4 version <span
        __postbox-detected-content="__postbox-detected-date"
        class="__postbox-detected-content __postbox-detected-date"
        style="display: inline; font-size: inherit; padding: 0pt;">3.4</span>
      with PG <span
        __postbox-detected-content="__postbox-detected-date"
        class="__postbox-detected-content __postbox-detected-date"
        style="display: inline; font-size: inherit; padding: 0pt;">11.0</span>
      and I get this error when I try to connect with scram
      authorization: <br>
      <br>
      User "myuser" does not have a valid SCRAM verifier. <br>
      <br>
      How do I get around this?  
      And also how would I do this for psql?<br>
    </blockquote>
    <p>You need to update the password using SCRAM I believe...</p>
    <p><code>See here:
        <a class="moz-txt-link-freetext" href="https://paquier.xyz/postgresql-2/postgres-10-scram-authentication/">https://paquier.xyz/postgresql-2/postgres-10-scram-authentication/</a></code></p>
    <p><code><br>
      </code></p>
    <p><code>JD<br>
      </code></p>
    <blockquote type="cite" cite="mid:5BD89A3D.5060108@sqlexec.com"> <br>
      Regards, <br>
      Michael Vitale
    </blockquote>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Command Prompt, Inc. || <a class="moz-txt-link-freetext" href="http://the.postgres.company/">http://the.postgres.company/</a> || @cmdpromptinc
***  A fault and talent of mine is to tell it exactly how it is.  ***
PostgreSQL centered full stack support, consulting and development. 
Advocate: @amplifypostgres || Learn: <a class="moz-txt-link-freetext" href="https://postgresconf.org">https://postgresconf.org</a>
*****     Unless otherwise stated, opinions are my own.   *****</pre>
  </body>
</html>

--------------3DC31E156D92D6B76F5D1DCC--




From michael@paquier.xyz Wed Oct  31 09:55:01 2018
Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gHnDY-0000v4-Vy
	for pgsql-performance@arkaria.postgresql.org; Wed, 31 Oct 2018 09:55:17 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gHnDX-0007kk-44
	for pgsql-performance@arkaria.postgresql.org; Wed, 31 Oct 2018 09:55:15 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <michael@paquier.xyz>)
	id 1gHnDV-0007jj-Ko
	for pgsql-performance@lists.postgresql.org; Wed, 31 Oct 2018 09:55:14 +0000
Received: from out3-smtp.messagingengine.com ([66.111.4.27])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <michael@paquier.xyz>)
	id 1gHnDQ-0004gH-Ja
	for pgsql-performance@lists.postgresql.org; Wed, 31 Oct 2018 09:55:13 +0000
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
	by mailout.nyi.internal (Postfix) with ESMTP id 080E0220B1;
	Wed, 31 Oct 2018 05:55:07 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
  by compute4.internal (MEProxy); Wed, 31 Oct 2018 05:55:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h=
	date:from:to:cc:subject:message-id:references:mime-version
	:content-type:in-reply-to; s=fm3; bh=2uWPczuZdXPLa1d5jUYS+a7oa57
	p2yO3kPlz96FMFyw=; b=kuMjoNVuvQVsDOamiY/HhwYMkUFbW0Ry8kYexlI+VyB
	WeQwn5VJ09UgNX3IyiYVVyyY7vPY7ifIoNqTblGZ4YABsrDD3KuiFQVOO2EZuaZ4
	2K5pWC3eEbCm4G1qaSNf3ykWGRgya9X3TbAL4147vDMpBzbOimpZ+cXh+txcqv9M
	oxMMncdf5au3Xrv1BpAB0PkShL2vM52+KZWysKXygUMJPRe7wah9+DoUzI3ktdB2
	SZJqxEWnNSkIqWxPd94tSp228UupDtWO7UVGYlTR/y6vx7xBZMzJPuNn7Pg+5F0Y
	MFT/LhktLZDad+DDFqtJJIuM7SNp+TV9EnA6Yn8OPdQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-type:date:from:in-reply-to
	:message-id:mime-version:references:subject:to:x-me-proxy
	:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=2uWPcz
	uZdXPLa1d5jUYS+a7oa57p2yO3kPlz96FMFyw=; b=grj10rRGmWiSIQ1EZMx42q
	dEd/5BN0+YQU+V2yO7woMjc1yxmwcYLF0UgX6E+6VcU+xDF+OzjJe9nndU5fYV3U
	DVi8vwRFe789bccxABHGHQTc65J3vyo6NVCEQv3ACMBPeLxKrE93OqWHPzEgCDCT
	oLv3981paRc/dBC5cNOrYdTfqHDG48Tl6c2/7xInUqPe1crETF5zjsBC+8SNplVD
	H4flDK3gWW7CUt++A/rEPfgjeNa7lMj853WtYFhU1dgSwHRT8ZQ8db68RObzKP/f
	radFmnni5JOvJ96xpvwvji7PSaPvJkZkhXBlcG1jyoKjMfxaKqmdFTqN6IlvozxQ
	==
X-ME-Sender: <xms:-nvZW7moAajq49qF4RLZCiGqA6IwOUoxSsl-FIfaHEuEfUTor655ug>
X-ME-Proxy: <xmx:-nvZW9nBwjTJrxTZeiniag6pzOg7DkOcjgbusYNEFAbrEaAbaOYbyg>
    <xmx:-nvZW1GAbMKppR0GmzgmavbmP05EPcTDl-MXbz9evdUsgkRksePo1w>
    <xmx:-nvZW9TwD-jDwpINP8BnWsJ0iwmM9-pPFGmoziz20jRPOJ74MMcTtA>
    <xmx:-nvZW94zt29uN9aVwiaGNplc3t5ci6QAJql3y1vf0dezeg-Kh8kGxQ>
    <xmx:-nvZW1MGHW60enF4z-ge-fn29cQfNruBhaeWRKo57P64LmtQHiOeTQ>
    <xmx:-nvZWy1vxNnEJYdpv9YA8ljNDiIR5anbMLSyiJ7vUR4cwnOhm03eGA>
Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162])
	by mail.messagingengine.com (Postfix) with ESMTPA id 8FA66102ED;
	Wed, 31 Oct 2018 05:55:04 -0400 (EDT)
Date: Wed, 31 Oct 2018 18:55:01 +0900
From: Michael Paquier <michael@paquier.xyz>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: MichaelDBA <MichaelDBA@sqlexec.com>,
	pgsql-performance@lists.postgresql.org
Subject: Re: SCRAM question
Message-ID: <20181031095501.GH7862@paquier.xyz>
References: <5BD89A3D.5060108@sqlexec.com>
 <7460ee84-6c64-dcbc-4fc6-c88507ccb2ee@commandprompt.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="Q59ABw34pTSIagmi"
Content-Disposition: inline
In-Reply-To: <7460ee84-6c64-dcbc-4fc6-c88507ccb2ee@commandprompt.com>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk


--Q59ABw34pTSIagmi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 30, 2018 at 11:03:14AM -0700, Joshua D. Drake wrote:
> On 10/30/18 10:51 AM, MichaelDBA wrote:
>> I am using pgadmin4 version 3.4 with PG 11.0 and I get this error when I
>> try to connect with scram authorization:
>>=20
>> User "myuser" does not have a valid SCRAM verifier.
>>=20
>> How do I get around this? And also how would I do this for psql?
>=20
> You need to update the password using SCRAM I believe...
>=20
> |See here:
> https://paquier.xyz/postgresql-2/postgres-10-scram-authentication/|

In order to do that, you would basically need to:
1) Switch password_encryption to 'scram-sha-256' in the server
configuration.
2) Issue an ALTER ROLE command to update the password (likely it is
better to use \password from psql as this would send a hashed password
to the server, which relies on the server setting for
password_encryption).
3) Make sure that pg_hba.conf is using properly scram-sha-256 where it
should as authentication method.

If you do not want to upgrade to SCRAM, it is of course possible to
still remain with md5.
--
Michael

--Q59ABw34pTSIagmi
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlvZe/UACgkQnvQgOdby
QH0y9Q/+LlKCDggWd+DBH2va7119+RypYLFXssNH5NbDXDv/Lri0aEj4nINHfEfp
VdXQmgti5GknEFqjDLYYCX5R82U/D7puwyvHfwZcRyap4Ze3UFyZiK0ApSb6pTS/
ti3Q/ztpE3B/L25eZlm6TP60v379rE7b7olSLG68U4Klnf4HposwYt88MK0i8xKx
4rsjiX+ypfFSBpMG4/HIz/BbewK3VVQLO4+Wd51ypQDC6GPljq+unoUU+IllAQv5
EbXYUXdDxsjWFojBXJ2f0rVOK16f6GE8NSEh4C3XJcOgbOTd/whTjBXaha4s34h5
Q++r/UUAqvCWt8L+vAoGxXtYoBpHBFdg6fdnkFFuvH7juJRNwOsF/7bohraPBMfo
YfnZj3Ipk+PG4Z2a0qrGE1qEsMEVnjchHRi+zrWtsU53dcvuKKt4/b7yVNI3YkHr
DMAhlsRss0nVxlcfv2/mo/h+yvTFbMpJ40bXjKm5o/kfufZa/MJfZj3nEzphvV/+
aOZ1KgNfUskVVmWzC5aEKVtcmuKd40ddZOn1HPmTF6tEc6lTRkdvInV88TP6GA1+
5HLaTQJdVZjTUkUQuaf+QPt2yYU8pAyIsopvIs2GXqycZJDbz3MPhl3v2lJvoA16
tsGg3VtqRKMwH5p4x9MXqXEDg6DU8OHl8TWmehfR15vssA17So4=
=yJSI
-----END PGP SIGNATURE-----

--Q59ABw34pTSIagmi--