full-disclosure - Odd packet?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <40B4D104.5010708@utc.edu>
From: jeff-kell at utc.edu (Jeff Kell)
Subject: Odd packet?

Valdis.Kletnieks@...edu wrote:

> 3) An amazing number of ISPs do *not* do proper ingress/egress filtering.

Well, when you're cranking gigabits sometimes those little checks can 
become a bottleneck.

Besides, safe routing begins at home.  If end-users (or endpoints) would 
do ingress/egress filtering, there wouldn't be a problem.  I'm not so 
certain we should place the blame on the core backbone for passing the 
packets it is sent without alteration.

Jeff