From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgcrypto: PGP armor headers |
Date: | 2014-09-30 14:37:01 |
Message-ID: | 542AC00D.2080303@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/29/2014 05:38 PM, Marko Tiikkaja wrote:
> On 9/29/14 3:02 PM, Heikki Linnakangas wrote:
>> Is there any real life examples or tools out there to generate armors
>> with headers with duplicate keys? RFC 4880 says:
>>
>>> Note that some transport methods are sensitive to line length. While
>>> there is a limit of 76 characters for the Radix-64 data (Section
>>> 6.3), there is no limit to the length of Armor Headers. Care should
>>> be taken that the Armor Headers are short enough to survive
>>> transport. One way to do this is to repeat an Armor Header key
>>> multiple times with different values for each so that no one line is
>>> overly long.
>>
>> Does anyone do that in practice? Is there any precedence for
>> concatenating the values in other tools that read armor headers?
>
> Maybe I just suck at $SEARCH_ENGINE, but extracting armor headers
> programmatically doesn't seem to be very popular. I could only find one
> example, which returned the last instance of the key. But that seemed
> to be more an accident than anything else; it wasn't documented and the
> source code didn't say anything about it. I also think that's the worst
> behaviour. If we can't agree on concatenation, I'd rather see an error.
May I ask you why you wrote this patch? What are you doing with the headers?
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2014-09-30 14:45:57 | Re: pgcrypto: PGP armor headers |
Previous Message | Kevin Grittner | 2014-09-30 14:15:48 | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |