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

From: eric at arcticbears.com (Eric Paynter)
Subject: IE

On Mon, July 19, 2004 4:46 am, nicolas vigier said:
> The real solution is to use a browser with no known vulnerability (and
> that's better if it didn't have a lot in the past), not to try to hide
> what you are using.

That's not always possible. Sometimes, changing the browser is a project
that will take months to complete (think: corporation with thousands of
PCs at hundreds of sites - it takes time to create the business case, get
funding, build/test the auto install package, retrain the end users,
etc.). In the period of exposure, any little bit helps (albeit,
minimally). This small change can probably be done in a couple of weeks
with no impact to the user.

-Eric

--
arctic bears - email and dns services
http://www.arcticbears.com