Large keyrings, GnuPG slowdowns/Seahorse segfaults

[Graham]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 15 Sep 2002 9:54 am, Shawn K. Quinn wrote:

> My apologies if this is too far off topic, but there doesn't appear
> to be a Seahorse-specific mailing list.
>
> Up until a few minutes ago (when I realized this was slowing down
> even standalone operation of GnuPG greatly) I had a >11 megabyte
> public keyring. This caused Seahorse to segfault after about a couple
> of minutes. I was mainly just curious if anyone else had experienced
> similar behavior from Seahorse?

Yes, I have.  The problem is that although GPG has marched on, adding=20
ever new facilities, front ends for it have become out of date.  With=20
the exception of GPA (which Werner says is being consolidated and=20
updated) there apears to be no activity at all in this area, and those=20
that exist only offer minimal keyring management.  I'd like to see for=20
Linux the equivalent of GPGShell in Windows, which although a=20
proprietary product (but free) allows you to have a PGP like interface=20
to GPG in which you can even alter settings and key bindings.

I suspect that Seahorse was written for earlier versions of GPG that had=20
a size limit on the keyring (though I do not know for sure, and my=20
emails to the developers go unanswered).

>
> I was also wondering where, if anywhere, on the priority list were
> optimizations for users with large keyrings. I realize average users
> will have keyrings of maybe 2 megabytes max, but shouldn't there
> should be some way of keeping things from becoming dog slow with
> large keyrings?

Large keyrings can now be accommodated by GPG, but I suspect (as I said=20
above) that development on front ends has ceased to accommodate this.
- --=20

Graham
GPG Key: send an email to encryption.keys@ntlworld.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Please sign and encrypt for internet privacy

iD8DBQE9hGvnIwtBZOk1250RAvs1AKC2wX5ukPu85wAbwvE9axQdgHxy/ACfSIN2
t6p3E2Jcd5T7IUTL8cBOkbQ=3D
=3DRBgM
-----END PGP SIGNATURE-----