On Mon, Feb 04, 2019 at 02:22:36AM -0500, Ineiev wrote:
>
> So now a harder question: what should we do? I see three basic
> possibilities:
>
> (0) drop gpg_key completely;
> (1) recommend gpg --armor --export --export-options=export-minimal;
> (2) convert gpg_key to meduimtext.
I went with (2)
On Sun, Feb 03, 2019 at 02:24:38AM -0500, Ineiev wrote:
>
> I thought the same, but it turned out that I'm just not very sociable.
> for example, key 3CE464558A84FDC69DB40CFB090B11993D9AEBB5 exports
> to a 84k long file because it has 125 signatures from other people;
> with gpg -a --export --expor
Hello, Bob, Karl;
On Sat, Feb 02, 2019 at 12:48:55PM -0700, Bob Proulx wrote:
>
> Ineiev wrote:
> > Currently the 'gpg_key' colunm of the 'user' table has the 'text'
> > type, this means 64k character limit. Some users attempted
> > to register longer GPG keys, and they were truncated.
>
> Long
Longer than 64K! That seems very long to me.
Maybe they included a big image. (Knowingly or not.)
Maybe it would be better to consistently report an error and reject the
upload, for the reasons Bob gave ... -k
Hi Ineive,
Ineiev wrote:
> Currently the 'gpg_key' colunm of the 'user' table has the 'text'
> type, this means 64k character limit. Some users attempted
> to register longer GPG keys, and they were truncated.
Longer than 64K! That seems very long to me. This feels to me
(without looking) that
Hello,
Currently the 'gpg_key' colunm of the 'user' table has the 'text'
type, this means 64k character limit. Some users attempted
to register longer GPG keys, and they were truncated. GnuPG 1.4
manages to import it, while complaining; GnuPG 2.2 tends to reject
such keys completely.
I think thi
