IE will be provided with a popup blocker which is laughably easy to circumvent, and the blocker will have a gaping security hole that allows any website visited to contain code that gains local administrator privileges. A patch will be released, and 3 percent of users will install it. Of those, ten percent will have to uninstall it because it breaks something else. Shortly thereafter the public exploits will begin, and Overly Critical Guy will defend the product and berate its users. Again.
I don't even know why this is a question.
Hire an SCO programmer? Have you seen their products? Completely aside from the ethical aspect, the people responsible for that work product should be ashamed of themselves.
"I was under a 5 year nondisclosure with pay in escrow."
I, for one, welcome our new cellular overlords.
Can they hear me now?
Re:Technology threats vs. Policy threats
on
RFID Hell
·
· Score: 1
A SSN is not an identification number for any purpose other than determining elegibility for benefits under the Social Security Act. Use of Social Security account numbers for any other identification purpose, or as part of or foundation of another identification code is a violation of law.
Microsoft has the dirty details on how SUN did the nasty plot with SCO against Linux. After SCO's crash and burn, they'll trash SUN. By the time the mud is dry they'll own it through a VC puppet company and it'll be "second verse, same as the first."
I create a new folder for each item. Then enough new parent folders to build a conceptual chain back to the primal item, or some other item in the extant tree. This would be useful except that my conceptual links tend to be one-way references, so the storage, while consistent, is write only.
OK, I may be a little off base here, but my inbound spam has dropped 99%. With every major ISP blocking the ports used by MSBlaster and Sobig.F (and incidentally Exchange clients) it seems we have gotten a reprieve from the deluge.
Here's a suggestion: When the Exchange servers and clients are updated to work around this, block whatever port they're using again. For the good of the net. Continue doing this until the irresponsible vendor of this malware can demonstrate (with source code!) that their app is not opening the door to this torrent of filth.
Re:SMTP IS DYING/DEAD
on
P2P Spam?
·
· Score: 3, Insightful
Erm, my sendmail install seems to still be working, and (checking) yes, it still delivers mail. SMTP seems to still be working.
It's Exchange that seems to be dead. Given the sudden dearth of enlargement offers in my inbox, I have to say "it's a good thing."
Most of the people who run websites think html formatting is "programming". It should surprise noone that given a pistol they make holes in their feet.
OTOH, IIS servers are insecure by design, as a quick glance at your logs will tell you. Where else would all those requests for/c/windows/cmd.exe? come from?
Let's face it. The web is always going to be the Wild Wild West.
As a result of the Homeland Security advisory, administrators at Internet service providers, including Cox Communications and AT&T Broadband, decided to cut their systems off from inbound access to the three ports recommended in the advisory: numbers 135, 139 and 445.
Unfortunately, blocking these ports cuts off several other legitimate applications, including the ability of remote users to get their e-mail from Microsoft Exchange servers across the public Internet.
So our respite is due to the fact that every MS Exchange server on the Internet has been neutered.
Yay!
How long have you been a perl programmer?
Hacker: Programmer who gets the job done.
Developer: Programmer who gets the job, wastes the first 95% of the development time, and hires a hacker to get the job done.
You fight the fight you must with the weapons at hand. The victor writes the history. Don't like that system? Change it. I dare ya.
I think we can attibute this to ISP's new attention to firewalling. I believe that in the light of Blaster many ISPs are filtering the ports that should have been shut down on Winoze boxes by default. Hence, the spamzombies are not getting their instructions. Our respite will probably persist until newly engineered spamzombie software is available. Recent experience says 3-4 weeks.
These batteries for these phones are chipped. Wrong chip and the phone discharges the battery, allegedly to protect the user from "substandard offbrand batteries." Thus, you have to buy approved batteries, or the phone catches fire.
Since the phone is designed this way, the burn victim should be able to recover damages from a manufacturer that designed a phone to explode when the phone does not approve of the battery.
How do you send a real letter? I researched this issue, and apparently it involves buying something called "stamps" and affixing them to a printout of your mail. Then you give it to the stalker in the little jeep that drives by your house each day.
It's forward-looking statements are amusing.
obligatory: beowulf cluster of all your STB belong to us - Darl.
IE will be provided with a popup blocker which is laughably easy to circumvent, and the blocker will have a gaping security hole that allows any website visited to contain code that gains local administrator privileges. A patch will be released, and 3 percent of users will install it. Of those, ten percent will have to uninstall it because it breaks something else. Shortly thereafter the public exploits will begin, and Overly Critical Guy will defend the product and berate its users. Again.
When the patches can be trusted to not break other stuff.
I quit reading their stuff when they started printing articles From Giga Group, Gartner and Rob Enderle as straight material. Don't feed the trolls.
Oldtimer: So what if you lose a few megs of mail now and then? Email is like Doritos. They'll make more.
I don't even know why this is a question.
Hire an SCO programmer? Have you seen their products? Completely aside from the ethical aspect, the people responsible for that work product should be ashamed of themselves.
"I was under a 5 year nondisclosure with pay in escrow."
I, for one, welcome our new cellular overlords.
Can they hear me now?
Of course it's done. That doesn't make it right.
If you cannot escape, you are enslaved. Resistance is only futile if you believe it is.
Microsoft has the dirty details on how SUN did the nasty plot with SCO against Linux. After SCO's crash and burn, they'll trash SUN. By the time the mud is dry they'll own it through a VC puppet company and it'll be "second verse, same as the first."
Introducing random letter sequencing adds randomness, which results in a larger file since the randomness is itself incompressible data.
I create a new folder for each item. Then enough new parent folders to build a conceptual chain back to the primal item, or some other item in the extant tree. This would be useful except that my conceptual links tend to be one-way references, so the storage, while consistent, is write only.
If they send Ballmer, Brazil might prohibit proprietary software altogether, so vehement was Villanueva's response (and so effective is Ballmer).
Next up, Texas!
Here's a suggestion: When the Exchange servers and clients are updated to work around this, block whatever port they're using again. For the good of the net. Continue doing this until the irresponsible vendor of this malware can demonstrate (with source code!) that their app is not opening the door to this torrent of filth.
It's Exchange that seems to be dead. Given the sudden dearth of enlargement offers in my inbox, I have to say "it's a good thing."
Not to be overly obvious here, but it appears to be working. A quarter million spambots are currently awaiting their marching orders.
OTOH, IIS servers are insecure by design, as a quick glance at your logs will tell you. Where else would all those requests for /c/windows/cmd.exe? come from?
Let's face it. The web is always going to be the Wild Wild West.
The aftermath of cyberattacks
So our respite is due to the fact that every MS Exchange server on the Internet has been neutered.
Yay!
How long have you been a perl programmer?
Hacker: Programmer who gets the job done.
Developer: Programmer who gets the job, wastes the first 95% of the development time, and hires a hacker to get the job done.
You fight the fight you must with the weapons at hand. The victor writes the history. Don't like that system? Change it. I dare ya.
I think we can attibute this to ISP's new attention to firewalling. I believe that in the light of Blaster many ISPs are filtering the ports that should have been shut down on Winoze boxes by default. Hence, the spamzombies are not getting their instructions. Our respite will probably persist until newly engineered spamzombie software is available. Recent experience says 3-4 weeks.
If you hadn't bought the penis enlargmenent pills you wouldn't be on their sucker list.
Since the phone is designed this way, the burn victim should be able to recover damages from a manufacturer that designed a phone to explode when the phone does not approve of the battery.
Seems a most chancy way to send a note.
Apologies to RAH
Actually, encrypted logins could enable them to bulletproff the interop ban if they wanted to, regardless of how good your fave IM coders are.