| nosedive admin 2006-01-30, 5:47 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
In <drknv0$hbh$1@bananasplit.info>, fleegle@bananasplit.info wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA512
>
>On Mon, 30 Jan 2006 09:39:13 +0000 (GMT), Anonymous wrote in
>Message-Id: <9be0dbccdb18a41026a87bec546a9c49@anon.bananasplit.info>:
>
>
>Yes, cleanfeed did kill it on my system as a binary in a non-binary
>group. I've whitelisted apa-s now to ensure this doesn't happen again.
>When I have time, I might modify cleanfeed to allow a higher binary
>lines count in specified groups, think this would be useful.
>
>Of course it doesn't make a lot of difference what I do if none of my
>peers propagate messages. The cleanfeed default allows 15 lines of
>binary-like data in a non-binary group. In this instance, I didn't
>filter the message as it didn't make it to me. I've added a couple of
>'suck' type peers to get around this.
Hmm.. I understand the idea of killing binaries in non-binary groups, but
it *should* be reletively easy (and seems perfectly sensible to me, a guy
who doesn't have to deal with an nntp server) to whitelist pgp keys and
reasonable sized blocks of encrypted text. especially in groups where
things like that are commonly used like a.p.a-s, alt.security.keydist,
alt.security.pgp and the several variations of a.a.m that I've seen just to
name a few. There's more that I don't know about I'm certain.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: cp850
iQEVAwUBQ929ar+xC5syX0FdAQH3dQf8CyetmHaf
waqGgA+Gzkl0E81UJflz0BJj
s0Z7hCJIZIkXjWrN/QlvCZaJQT+6wp+vBORCehoffsym/ZAB0hMooY//84K05oFO
YJO9cGhnj4i4X2dv7X1kapxxsHDhq7gqiFYlMWb2
MUPzrV2YG1tInH9/lHqMv9M+
UbaEsm+SaVGl1XnMu/+dRWv/ DEClXyYXYqoMG7ua+ZI5KwoGta12ymA7hgjk1At2
YFM9I63A6WwII81zseiQ6Yab0/nvYxjP3TKD51xJSEgAnlwUcP7ebXtf4O17XfUw
HY7hViJfOfMDVjV0wCKyuyE6zRlSXnizkX/YeN+oTsDTYx0yhdQ4vw==
=q0v5
-----END PGP SIGNATURE-----
|