Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

A Solution for Spam/Virus/Zombie (ThreatNet Lives!) More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Abuse protection? (Score:1)

by Aristotle (5147)

How will you prevent hosts from maliciously reporting other, innocent hosts as miscreants?
- Re:Abuse protection? (Score:1)
  
  by Alias (5735) on 2005.03.20 19:39 (#39032) Homepage Journal
  
  Luckily, that isn't my problem. The problem of trust is one that each network operator will have to deal with.
  
  All I can do is to not mandate a particular solution, and instead to let evolution decide.
  
  On my company-internal ThreatNet, I simple have the server only allow connections from IPs inside my network.
  
  On a commercial one, perhaps we use SIRC, passworded accounts and certificates to verify validated users.
  
  I imagine there are a number of different solutions to the trust problem.
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.