Nomen Nescio writes:

I've posted it a couple of times, here.
Check the dashes at the beginning and end of the block. Sometimes (don't
know why) it goes through with a dash & space added (- -----) when it should be
(-----). Just delete the dash & space before adding it to your ring.
Then, of course, check it against a previous post to verify that it came
from me.

Well, actually I was hoping for a separate source for the key. A public key
posted in a USENET post isn't very useful for verifying a USENET post, since
it's not an out-of-band source.

In my case, my public key is on my Web site, so anyone can download it and at
least be sure that whoever signs my USENET messages also controls my domain
and Web server, which is a pretty good indication that I am who I claim to be.

I think my public key is also on a couple of servers, but I'm not sure (the
servers themselves don't always strike me as very stable).

It's always a good idea to put a PGP sig on your posts. Headers can
be forged. But if someone is duplicating a PGP sig.......They're probably
NSA.

Signing things that don't need to be signed is an unnecessary security risk.

I had someone try to impersonate me on another group about 6 months
ago. The idiot copied my PGP sig from another post I made. When I
exposed the fraud, someone else verified that the sig was corrupt and
that the post was a forgery. Once you put your sig on something, every
word, sentence, space, and comma is set in stone and tied to you, alone.

Yup.

Did you file a complaint with Dizum M2N, yet?

No. I'm not convinced that it's that big a deal. People who are smart enough
to care about whether or not it's really me are also smart enough to spot
impersonations--just the style of writing alone gives it away. And those who
aren't smart enough don't matter.

--
Transpose mxsmanic and gmail to reach me by e-mail.