PGP trust paths : Alexander Schremmer → ct magazine CERTIFICATE

from	stats  Alexander Schremmer <alex.at.alexanderweb.de>
to	stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de>
find	reverse path
see also	paths image by wotsap

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	0CB7356A  stats  Andreas K. Huettel (at home) <mail.at.akhuettel.de> #918 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	CF3401A9  stats  Elmar Hoffmann <elho.at.elho.net> #36 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	E10F502E  stats  Marcus Frings <protagonist.at.gmx.net> #14 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	7887F787  stats  Andreas K. Huettel (at work) <mail.at.akhuettel.de> #900 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	4DD9D1C4  stats  Marcus Wolschon <Marcus.at.Wolschon.biz> #1646 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	BAB58229  stats  Marcus Frings (Work) <marcus.frings.at.oc.rwth-aachen.de> #13 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	E4B9A3A1  stats  Boris Stobbe <bstobbe.at.uni-paderborn.de> #4213 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

0	4FC59E44  stats  Alexander Schremmer <alex.at.alexanderweb.de> #433 signs
1	1DFBA164  stats  Bernhard Wiedemann <bernhardpgp.at.lsmod.de> #1046 signs
2	B3B2A12C  stats  ct magazine CERTIFICATE <pgpCA.at.ct.heise.de> #158

PGP pathfinder & key statistics

• input : key id's of length 8, 16, 24, 32 or 40, optionally preceeded by 0x, in upper or lowercase, like

  FC243F3C      0xfc243f3c

• example : find trust paths from D5327CB9 (Wietse Venema) to FC243F3C (me)

• If you have a PGP page, visitors may want to find trust paths to your key ; here is what I use :

  your key id :

  To make this work for you, just include this piece of html :

    <FORM METHOD="GET" ACTION="http://pgp.cs.uu.nl/mk_path.cgi">
    your key id :
    <INPUT TYPE=TEXT    NAME=FROM   SIZE="10">
    <INPUT TYPE=HIDDEN  NAME=TO     VALUE="********">
    <INPUT TYPE=SUBMIT  NAME=PATHS  VALUE="find trust paths to me">
    <INPUT TYPE=RESET   NAME=reset  VALUE="reset">
    </FORM>

  and replace ******** with your key_id.

• For plots, facts and figures see the analysis of the strong set in the PGP web of trust.
• For details, see the pathfinder FAQ - frequently asked questions.