full-disclosure

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-next>] [day] [month] [year] [list]

Message-ID: <20030716204513.B4E47C305@relayer.avian.org>
From: hobbit at avian.org (*Hobbit*)
Subject: cisco

   workaround would be to firewall the router's own IP address(es).  This 
   would still allow the router to perform its routing function for other IPs

Y'mean this *still* isn't done as standard best practice?

*sigh*  ... well, perhaps not, because of speed considerations, real
or perceived, from slapping an ACL on an interface.  Can't accept a minor
slowdown in the interest of security, now can we?

In the interest of addressing this in an efficient manner, particularly if
anyone from cisco is listening, how 'bout this:  Implement some way for an
interface processor to recognize a small set of source or destination
addresses, i.e. the router's own set, and push packets involving them
up to process-switched level where a special ACL handles all the "to/from
ME" traffic.  Perhaps define a new interface type to hang it on, but do
retain a notion of which interface a packet came from during processing.

Is there some other minimal-impact workaround these days?  I'm pretty
out of touch with cisco "sales engineer" pablum lately.

_H*