Hi On Fri, Sep 09, 2016 at 10:02:04AM +0200, Guilhem Moulin wrote: > Hi, > > On Fri, 09 Sep 2016 at 10:56:39 +1200, Andrew Ruthven wrote: > > The regular expressions in sig2dot don't match the new output format > > in gpg 2.1 > > > > The new output format is (using the same keys as in the script): > > > > pub dsa1024 2003-08-01 [SC] > > 75D8908EBD35E31D94D102EF10557B83807CAC25 > > uid [marginal] Michael Ablassmeier (abi) <[email protected]> > > sig 3 CE04080E9456ADE2 2004-02-07 Michael Schiansky > > <[email protected]> > > I'm not sure whether it's worth to fix this: gpg's output without > --with-colons is designed to be human-readable, not machine-parseable. > Furthermore there is no guaranty that the format won't change across > versions (as you just pointed out :-P). Passing the ???--keyid-format??? > option with a value other than ???none??? will make sig2dot work again with > 2.1.15. But I think on the long run the proper fix would be to rewrite > sig2dot to make it read the colon-separated input produced by ???gpg > --with-colons???.
I have not looked in detail, but there seem to be at least one rework of sig2dot rewritten which seem to cover this. It is https://github.com/bmhm/sig2dot2 Commits stop as well on beginning of 2019 though. Regards, Salvatore
