progs/catsign.c; Verify equality of keys more directly.
Rather than comparing the two keys' `id' slots, just compare the
pointers. It's not like we got them from different keyrings or
anything. This makes it clear that we're checking that we really have
the /same/ key, found by two different paths.
Fortunately, this isn't a security problem: the code in `key/key-io.c'
won't allow two keys with the same `id' value to exist in the same
keyring. This change therefore doesn't have any observable effect.
But, seeing as I just had a panic regarding a potential security hole in
`tripe-keys', it's as well to make it clear what's actually going on.
~mdw / catacomb / commit