config services signature/signers and metadata message types

[jeffgrunewald]

allow management of signing keys for oracles to verify requests coming to the config server (from the verifier for instance)

[andymck]

I assume the inclusion of signer here is to help with enabling multiple known signing keys to be available rather than assuming a single signing key ?

[jeffgrunewald]

I assume the inclusion of signer here is to help with enabling multiple known signing keys to be available rather than assuming a single signing key ?

I came around on this from an earlier decision, actually; now that I have an idea of all of the different authorizing keys the config service has to manage I think it makes more sense to have the request or supply it’s own pubkey (should be a cheap operation) and then have the config server only verify the signature of that single key and check for membership of that single key in its collection of authorizing keys (another cheap operation) rather than looping over all of the keys it manages and checking for the one that signed the request (increasingly expensive)