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

Message-ID: <200307170955.44682.carl@learningshophull.co.uk>
From: carl at learningshophull.co.uk (Carl Livitt)
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?

Or, in the case of business users with a Cisco ADSL router that is remotely 
managed, it's not possible for a customer to firewall the interface - it's 
plugged directly into the ADSL line.

In our case, our provider simply asked 'What Cisco advisory?' when I called 
them about it this morning. I had to forward the advisory to them myself and 
am still waiting....

Sheeesh.