Just a few comments...
Steve Gibson has passion and I respect that. Furthermore, much of his site is written in layman's terms albeit from a soapbox point of view. For this reason alone, I know of at least one very large ISP who directs customers to his site when trying to explain the dangers of not applying the appropriate security patches to their machines. Real security sites like
Security Focus and
Incidents.org, while much more accurate than GRC, are far too technical for the vast ranks of near computer-illiterate subscribers. So in this respect, if GRC's ranting manages to light a fire under their collective arses to stay up-to-date with security patches, then so be it. Until a group of BOFHs get together to design a security site with the layman in mind, directing them to GRC is probably better than not doing anything.
In the past, I've looked upon Steve Gibson with a sort of bemusement. There are plenty of kooks out there (
Alex Chiu anyone?). Here's one who's at least trying to do something good. The three biggest problems I have with Steve Gibson are a) his ego, b) his apparent tendency to work in a vacuum and c) his soapbox approach.
There are already plenty of big egos on the net. D.J.Bernstein comes to mind (like him or hate him, you have to respect his numerous contributions to security and the internet). So adding one more ego to the fire doesn't really really matter. In fact, it's quality amusement when two big egos clash.
His work in a vacuum, though, really gets me. What I mean by that is he doesn't seem to keep track of what's going on in the security world. GRC's recent
SYN-attack countermeasures are a perfect example. In his own words he says "I was unaware of previous work in this area" and judging from the problems left unaddressed by his solution, I have to believe him. The problem here is that no "security expert" (and indeed, no
programmer!) should operate without following other developments in the community. Had GRC bothered to look around to see if any work for had been done towards combatting SYN attacks he surely would have stumbled upon DJB's and Eric Schenk's SYNcookie method and he would have learned that the Linux kernel has had such an implementation for around years now.
I've already talked about his soapbox approach.