<$MTInclude module="DTD"$> <$MTBlogName$>: <MTIfNotSpecificComment>Comment on <$MTEntryTitle$></MTIfNotSpecificComment><MTIfCommentVerification>Verify PGP-Signed Comment</MTIfCommentVerification> <$MTInclude module="HeaderLinks"$> <$MTInclude module="MathJax"$> <$MTInclude module="ShadowStart"> <$MTInclude module="SmallBanner"$>

Respond To:Verify the PGP-Signed Comment:

<$MTEntryTitle$>

Posted by <$MTEntryAuthor$> at <$MTEntryDate$>

"><$MTCommentSubject$>

Posted by <$MTCommentAuthor$> at <$MTCommentDate$>

Your Comment:







Remember personal info (requires cookies)?

Text filtering options:

Convert Line Breaks
The default conversion: 2 linebreaks start a new paragraph; one linebreak inserts a <br />.
itex to MathML
Raw HTML (you need to insert all your <p> tags by hand), but with embedded itex equations.
itex to MathML with parbreaks
Embedded itex, and 2 linebreaks start a new paragraph.
Markdown
John Gruber's Markdown formatting.
Markdown with itex to MathML
Markdown formatting with embedded itex.
Textile
An XHTML-friendly implementation of Dean Allen's Textile formatting.
Textile with embedded itex to MathML
Textile formatting with embedded itex.

Allowed HTML tags: <p>, <br />, <blockquote>, <pre>, <b>, <u>, <i>, <tt>, <strong>, <em>, <code>, <ul>, <ol>, <li>, <dl>, <dt>, <dd>, <sup>, <sub>, <abbr title="">, <acronym title="">, <bdo dir="" xml:lang="">, <span xml:lang="">, <a href="" title="">.

PGP-signed comments are encouraged.

" /> " />


Previous Comments & Trackbacks:

Original Post:

<$MTEntryTitle$>

<$MTEntryBody process_tags="1"$> <$MTEntryMore process_tags="1"$>

Posted by <$MTEntryAuthor$> at <$MTEntryDate$>

<$MTCommentSubject$>


Interpreting the verification results

The above comment was digitally signed using PGP. The Public Key used to verify the signature was downloaded from the URL listed above. Hopefully, the signature was valid, the UID corresponds to <$MTCommentAuthor$> and the URL from which the key was fetched corresponds to <$MTCommentURL$> (or some other website controlled by <$MTCommentAuthor$>). If so, you can have a high degree of confidence that <$MTCommentAuthor$> authored the comment. Conversely, if the URL from which the key was fetched doesn't belong to <$MTCommentAuthor$>, then you have serious reason to doubt that <$MTCommentAuthor$> wrote the comment.

If the signature was invalid, there could be many things going on.

  • Perhaps the signing key was unavailable.
  • Perhaps the commenter spooged the process of signing their comment, and pasting the signed comment into the comment-entry window.
  • Perhaps something is wonky with the system.
  • Or perhaps someone is trying to pull a fast one, grafting a previous signature by <$MTCommentAuthor$> onto a message of their own choosing.

In any case, you should be suspicious, and might try manually verifying the “raw” PGP-signed comment from the textbox above. You'll need <$MTCommentAuthor$>'s PGP Public Key to do that. You'd be best-off obtaining it directly from <$MTCommentAuthor$>.

<$MTInclude module="ShadowStop">