Managing the WoT with GPG

[martin f krafft]

also sprach Neal H. Walfield <neal at walfield.org> [2017-06-21 11:53 +0200]:
> > 3. Is there a way to run --check-trustdb or --update-trustdb not
> >    over the entire key graph, but only traversing to a certain depth
> >    starting from a specific key? Then I could tell parcimonie to run
> >    --check-trustdb for every key it imports, or have mutt run
> >    --update-trustdb for every key I want to use. This would
> >    iteratively achieve the job with the benefit that no cycles would
> >    be wasted processing trust for keys I never use. I understand
> >    --edit-key can be used to change the ownertrust, but I don't
> >    think it recomputes the WoT on change, does it?
> > 
> >    If there's no way to do this yet, would this be a useful addition
> >    to the UI, assuming it's technically possible?
> 
> This isn't easy given the current implementation: GnuPG doesn't store
> the graph, but traverses the graph and only saves whether a particular
> key is trusted.

It's gotta start somewhere, though, right? Can't it pick the leaf
where to start?

-- 
@martinkrafft | http://madduck.net/ | http://two.sentenc.es/
 
dies ist eine manuell generierte email. sie beinhaltet
tippfehler und ist auch ohne großbuchstaben gültig.
 
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: digital_signature_gpg.asc
Type: application/pgp-signature
Size: 1118 bytes
Desc: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
URL: </pipermail/attachments/20170621/e1c172a8/attachment-0001.sig>