GnuPG 1.2.1 trustdb checks for every pubkey import?

[Ingo Klöcker]

--Boundary-02=_AONY+1saNcqcj01
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Thursday 27 February 2003 09:21, Werner Koch wrote:
> On Wed, 26 Feb 2003 23:11:21 -0500, gabriel rosenkoetter said:
> > Every time a key is added to my public keyring, GnuPG forces a
> > trustdb check. Has anyone else experienced this at least absurd and
> > arguably broken behavior?
>
> No, that is not broken but indeed required.  By importing a new key
> you may change the WoT, GnuPG must check this.  This is a simple and
> straightforward strategy.

But it could be improved a lot. In most cases it's unnecessary to=20
recalculate the complete local WoT just because of one new key. Of=20
course, an algorithm which only recalculates what is necessary is much=20
more complex then the current straightforward algorithm.

Regards,
Ingo


--Boundary-02=_AONY+1saNcqcj01
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+YNOAGnR+RTDgudgRAgnIAJwL7FMYTKFpdDXVr1Sc/HrPYPxjxwCfdjIe
qMy6072hEPgRWheZPW+nKw8=
=3cZU
-----END PGP SIGNATURE-----

--Boundary-02=_AONY+1saNcqcj01--