Re: ERROR: Corrupt ascii-armor

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: VENKTESH GUTTEDAR <venkteshguttedar(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: Corrupt ascii-armor
Date: 2014-11-17 18:14:03
Message-ID: CAMkU=1wTd0SqhNihB5EJGywZBnkeZkXhjW=adiPpGD1A_FtqPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 17, 2014 at 3:00 AM, VENKTESH GUTTEDAR <
venkteshguttedar(at)gmail(dot)com> wrote:

>
> INSERT INTO testuserscards(username, cc)SELECT robotccs.username,
> pgp_pub_encrypt(robotccs.cc, keys.pubkey) As cc
> FROM (VALUES ('robby', '41111111111111111'),
> ('artoo', '41111111111111112') ) As robotccs(username, cc)
> CROSS JOIN (SELECT dearmor('-----BEGIN PGP PUBLIC KEY BLOCK-----
> super publickey goobly gook goes here
> -----END PGP PUBLIC KEY BLOCK-----') As pubkey) As keys;
>

Can you simplify that to the simplest case which shows the problem?
Probably just the 'select dearmor(...)'.

It doesn't like something about your public key. Since you censored that
data, there isn't much we can say about what specifically it did not like.

Cheers,

Jeff

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Haas 2014-11-17 19:08:39 Re: [HACKERS] Performance issue with libpq prepared queries on 9.3 and 9.4
Previous Message Robert DiFalco 2014-11-17 17:55:47 String searching