On Mon, Nov 14, 2005 at 10:41:29PM -0800, "Hal Finney" wrote:
Your 0x40 is more than "human-readable", it is "should be displayed". I
don't like the idea of putting in a feature which burdens implementations
to do certain things in the UI, unless we have a very good reason.
Our PGP software might have to pop up dialog boxes to deliver these
notification messages, which I'm sure would bring objections from our
Unless it already doesn't pop up dialog boxes then it shouldn't pop up new
ones. All I suggest is adding text to the report about successful
verification, if such a report exists.
If and when we come up with a compelling reason to add such a UI mandate
in our data-format specification, then we could consider it. We would
also need to clarify when it should be displayed for key signatures: if
a web of trust is used, should we display all notations for all keys in
the chain that were used to establish the trustworthiness of a target key?
Definitely not. You only display the notation, if the successful
verification of the signature is explicitly reported to the user.
Should this happen on both encryption and signature verification? And is
it enough to do it once and consider the user "notified", or should it be
done every time?
The answers to questions like these are likely to be application specific.
That is, for some kinds of notations we would do it one way, and for other
types of notations we would do it another way. Maybe some would only be
for data signatures and not key signatures, or vice versa. Maybe some
would only be displayed for signatures on the key being used, while others
should be displayed for the whole trust chain. It depends on the purpose.
But isn't that dependence on signature type already resolved by the
different ways in which applications report on successful signature
verification? I was a bit sloppy first by saying that such notation should
be displayed upon successful verification. That is obviously wrong. What I
really have in mind is that such notation should be included in reports of
successful verification, if such reports are provided.
Putting in this 0x40 flag now, or any mandate for notation packet display,
will require possibly substantial change to every OpenPGP implementation
in existence. Sure, it potentially gives you a lot of leverage to
implement your desired new feature. But it is at a great expense.
We can't go forward with something like this without an extensive
discussion involving many groups, including UI experts.
Okay, there is no urgency. But I still think, it is a legitimate feature
which does not require dramatic changes on implementations' part. At the
same time, it substantially decreases the roll-out costs of many
applications, not just mine. Basically, it would enable people to do more
things without having to write sofware. The "note from one person to
another" is a nice feature to be included in signatures. If, for obvious
reasons, 0x80 cannot carry this semantics, some other flag should.
The true issue here, as I see it, is that indeed, one can change the
semantics of notation wihout owning it. If notation flags are not
considered part of the notation (that is, their use is not restricted by the
notation specification), then such flags are more or less part of the
notation value, and should convey information only about the value part
(e.g. whether it is text, image, boolean, etc.). If this is the case, it
should be included in the wording of the standard.
In that case, the feature I would like to see will have to be implemented in
a completely different fashion, but still preferably in the standard, as it
is generally useful. On the other hand, I think that notation flags should
be part of the notation spec; you cannot put binary data where the spec
requires text, so the spec may as well specify what flags to use and how
with the notation, even though the flags' semantics is the same across all