The only place there is a plethora of options (and I have taken
these as being options for the user to choose rather than the
implementor; and so have implemented all of them) are the eight
possible ways to identify yourself as the sender of a signed
message. Some of these (especially involving arbirtary strings)
seem to offer the possibility of signed messages that whose
origin cannot be authenticated. However, a good user agent will
point out to the user the implications of any particular
signature
- this is from A(_dot_)Young(_at_)cs(_dot_)ucl(_dot_)ac(_dot_)uk and I
trust it because...
- this claims to be from
A(_dot_)Young(_at_)cs(_dot_)ucl(_dot_)ac(_dot_)uk but I can't verify
that [without such-and-such further information]
- I ain't got no clue who this one is from
and if this is done properly there should be no problem.
Agreed!
Jim