Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security FullDisclosure
[Top] [All Lists]

Re: [Full-Disclosure] Re: Addressing Cisco Security Issues

Subject: Re: [Full-Disclosure] Re: Addressing Cisco Security Issues
Date: Tue, 30 Mar 2004 00:33:04 +0100
Whilst I can see your point, when you have an exploit for which there is
a widely-published vulnerability publicly available, would it not be
easier to simply offer the software to those who want it. I know that if
the next time an apache vuln came out, I had to contact someone at
apache to get them to give me the update so that I could stop my server
being vulnerable, I wouldn't be very happy. If there are publicly
available exploits, there should be publicly available patches.
Luke

Clayton Kossmeyer wrote:

The TAC process for this is to direct customers to their ISP for
downloads.  The reasons for this are many, but one of the major ones
is that SPs/ISPs want to control what versions of software are
deployed within their networks.






<Prev in Thread] Current Thread [Next in Thread>