Steve Gibson brags on his web site how he read the RFC for IRC and easily was able to act like a super Op. If it's that easy to find holes in the protocol, then why not just add a few security measures to the protocol and have the servers update their software? Sendmail, BIND, and the like are always updating their server software. Won't someone maintain ircd?
Yes - it's tragic that the large IRC networks may be going the way of the dinosaurs. Then again, then last time I personally was on EFNET was at least 6 months ago. The last ime I used it regularly was more than 2 years ago.
There's always more to learn in any discipline whether it be technology, law, or basket weaving. One could easily stay in one career for the rest of his or her life.
Recent proposed legislation appears to be even more egregiously devoid of thought and background knowledge than prior proposals. Rather than have my head explode while trying to fathom the depth of ignorance that is responsible for the more spectacular accusations against technology, I'm going to change careers and become a lawyer. Our friends in the Capitol appear to be playing a game that we can only win on their turf.
My question: OK, so I'm now a lawyer with a formidable background in all the technology that/. Readers love. What do I do to educate our lawmakers? Do I become a lawmaker myself? Do I run for office? Do I sell out? Do I litigate? Litigation seems to be working against tobacco, but not perhaps not against Redmond
Let's all simply block Microsoft IIS
on
Nimda To Strike Again
·
· Score: 2, Informative
The boss of my boss of my boss (his rank is somewhere around a full bird) asked me personally and the rest of the staff in earshot to encourage the entire enterprise (around 20,000 white-collar workers) to get off IIS. Although all MY web servers are Apache, most at the Enterprise are M$. We have never used Outlook and never will.
Well, I suggest that we go farther. We already block harmful and suspect viruses at our perimeter and throughout the enterprise. Why not instruct our routers, firewalls, and proxies to block any packets that indicate the content is coming from IIS - and block any M$ Internet Explorer broswer? Just drop the packets?
OK. I'm speaking toungue in cheek, but I could actually make a justifiable argument that such use has PROVEN twice in a month that those tools are demonstrated security risks and should be defined as dangerous activity.
Steve Gibson brags on his web site how he read the RFC for IRC and easily was able to act like a super Op. If it's that easy to find holes in the protocol, then why not just add a few security measures to the protocol and have the servers update their software? Sendmail, BIND, and the like are always updating their server software. Won't someone maintain ircd? Yes - it's tragic that the large IRC networks may be going the way of the dinosaurs. Then again, then last time I personally was on EFNET was at least 6 months ago. The last ime I used it regularly was more than 2 years ago.
Recent proposed legislation appears to be even more egregiously devoid of thought and background knowledge than prior proposals. Rather than have my head explode while trying to fathom the depth of ignorance that is responsible for the more spectacular accusations against technology, I'm going to change careers and become a lawyer. Our friends in the Capitol appear to be playing a game that we can only win on their turf.
My question: OK, so I'm now a lawyer with a formidable background in all the technology that /. Readers love. What do I do to educate our lawmakers? Do I become a lawmaker myself? Do I run for office? Do I sell out? Do I litigate? Litigation seems to be working against tobacco, but not perhaps not against Redmond
Well, I suggest that we go farther. We already block harmful and suspect viruses at our perimeter and throughout the enterprise. Why not instruct our routers, firewalls, and proxies to block any packets that indicate the content is coming from IIS - and block any M$ Internet Explorer broswer? Just drop the packets?
OK. I'm speaking toungue in cheek, but I could actually make a justifiable argument that such use has PROVEN twice in a month that those tools are demonstrated security risks and should be defined as dangerous activity.