-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In writes:

[...]

__Please be aware__ that this mini-flood, and the big flood on
12-27, were NOT the result of poor or flawed software. These
flooders have discovered the technical means to completely bypass most
(all?) moderation setups. (The method has been out there for years,
but has been relatively secret until recently.). Hopefully, the
movers and shakers of usenet will come up with better technical
and/or legal ways to _decisively_ stop this in the future.

ron schompert
(original proponent of rpm)




Hi Ron,

My recommendation to the moderation team would be to implement PGPMoose:

http://www.killfile.org/pgpmoose/

If the team decides to stay with ReadySTUMP for the next year, have Igor
set it up for you. STUMP has the capability to support PGPMoose
built-in, and its configuration should be well within the custom
programming support that he provides to you for the ReadySTUMP
subscription. If you decide to switch to the Panix STUMP, then PGPMoose
(via a GnuPG key) is already provided.

PGPMoose can serve as an additional "tripwire" on your newsgroup to
quickly detect forgeries, especially one-off forgeries versus floods
that would be detectable by CleanFeed. There are cancel-bots running on
the net that can send old-style cancels, and new-style authenticated
"NoCeM" messages, in response to PGPMoose signature failures. Many
sites directly support such automated cancellation of forgeries. The
killfile.org maintainer above will just need your public key to add to
the cancel-bots.

This is admittedly based on a small sample size, but it appears to me
that newsgroups that are protected by PGPMoose are much less subject to
direct forgeries, MI5 or otherwise.

- --
Paul W. Schleck

http://www.novia.net/~pschleck/
Finger for PGP Public Key

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (SunOS)

iD8DBQFHgB5N6Pj0az779o4RAlG4AJ9Jx4PxVzntzriMIY1yKj j317FuUQCgw6Dc
zV6btkDBLEOeCGIdWL9jNkM=
=rC9u
-----END PGP SIGNATURE-----