From: | Joe Snikeris <joe(at)snikeris(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Documentation for pgp_pub_decrypt |
Date: | 2016-09-26 23:03:59 |
Message-ID: | CAAnmyZZ14HjZbtDokn1Sc21-DrotHmwBNOPHjp+Cd0pyp82YYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Thank you. Your response helped me figure out why pgp_pub_decrypt wasn't
working for data that was encrypted outside of pgcrypto. The marker you
mention must be added by pgp_pub_encrypt? Perhaps it's worth mentioning in
the documentation that pgp_pub_decrypt is only intended be used on data
encrypted with pgp_pub_encrypt since it's unlikely that a user is going to
add that marker themselves.
On Sep 26, 2016 3:44 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> joe(at)snikeris(dot)com writes:
> > The following documentation comment has been logged on the website:
> > Page: https://www.postgresql.org/docs/9.5/static/pgcrypto.html
> > Description:
>
> > I believe the first argument should be of type 'text'. Especially
> > considering the paragraph that follows discusses how passing in bytea is
> > disallowed.
>
> No, that's how the function is declared. Maybe the following para isn't
> clear enough. What it's talking about is that the encrypted message has
> to contain a marker saying it was originally text.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | napocoelho | 2016-09-28 17:39:07 | Translation to Portuguese |
Previous Message | Tom Lane | 2016-09-26 19:44:37 | Re: Documentation for pgp_pub_decrypt |