I don't necessarily think it's astroturfing; it's a legitimate problem, and will continue to happen. OTOH, there are possible solutions, not only to this problem, but others as well. DBP, anyone?
He also recommended that customers who encounter the problem not restart their computers.
Obvious jab at Windows and the three-a-day reboot plan aside, this is just dumb. In fact, the whole situation is just dumb. Why does it seem that Symantec/Norton <insert product here> consistently makes a bad situation much, much worse?
They're talking about patches, bugfixes, etc. etc. etc. Windows Update is easy and intuitive, and takes about 2 minutes to do (and 2 minutes to teach someone how to do it). No such luck on a Linux platform.
I might just use RHN or Red Carpet, or one of many others to patch and upgrade a few hundred Linux boxes in 10 minutes.
Are application level firewalls sophisticated enough to allow machines on your internal network to advertise services to the Internet?
Nope. That should never happen.
The problem here is that application-level firewalling is fraught with problems. The lack of intuitive management for this type of firewalling is a problem that quite a few companies are trying to solve -- with limited success, so far. The problem is that as you move up the OSI layers, the variables increase exponentially. If you think that 65,536 is a big number, try writing an application-level script that permits "acceptable" MAPI requests while denying "unacceptable" MAPI requests. How do you determine that this NFS packet is good, and this one is bad? From the same host to the same server? How about X11? SSH? Oh, and don't break anything while you're at it. Lions and tigers and bears, Oh my!
These are the problems of an immature technology. As time passes, these issues might be somewhat mitigated, but there are plenty of "network administrators" that haven't fully grasped the concept of IP, and struggle with L3/L4 firewalling, to say nothing of moving up the stack.
Here's a tip, though; look for Bayesian filters in firewalls in a few years. That will be a trip.
Someone probably deserves recompensation for the hassle, but it's looking like the Internet has proven resilient to even this "high level" attack.
At what cost? Routers are working harder, code has been introduced into core servers that has no technical reason to exist, and an IP address, or possibly a sizeable range of IP addresses are now blacklisted worldwide. Those IPs won't be usable for anything anymore, or at least until we see widespread adoption of IPv6. *cough*
What the Internet doesn't need is to become even less of an end-to-end transport, less reliable. And we did it to ourselves.
The Linux drivers provided by Promise are, IMHO, a POS. Pain to compile. No management software. Diagnositics are limited. As a result, I'd go with a different IDE controller card if you want it for Linux. YMMV.
I'm with ya.
I've been running a Promise SuperTrak 6000 for a a little more than a year now. It's been reliable, but there are NO useful diagnostics, no management, and the pti_st modules are sketchy.
That said, it's been very reliable on 2.4.20; I haven't lost a byte. *knocks wood*
Please read the rest of this thread to get the general idea. Home users want things to work, period. They think in binary, even if they don't know it: "It works" or "It doesn't work".
The issue is with the lack of acceptance of patch download/installations, and the saturation of low-bandwidth links while downloading SP[1-9] at 100+MB.
Moderators, think before moderating. Posters, think before posting, please.
Automatic protection from running applications that break following a patch? At least a corporate user can call the helpdesk, while a novice home user would have no idea why something stopped working suddenly, and would chalk it up to "Computers are evil".
The divide between the tech-aware and tech-unaware grows exponentially.
No, the best solution is to have a separate, offline copy of known good md5sums to compare against. Ones that came directly from the developer, preferrably signed by the developer's GPG key.
This is exactly what I said. They should have been backing up the sums to removable media every night/week or whatever. It's simple, and makes lots of sense.
It's really a matter of hardware and longer development cycles. For instance, it's hard to get HP FC HBA drivers for RH8/9, but drivers for RH AS 2.1 are available. This is true for a number of HBA vendors. The same can be said for other vendor provided drivers. They don't want to release binary-only modules for 15 revs of the kernel if they don't have to.
The other side is the longer release cycle. A server doesn't need everything and the kitchen sync, but relies upon the viability of the core applications. On AS, this code is arguably more stable, and minimizes the "extra" code. Also, anyone doing Oracle on Linux needs AS 2.1, hands down.
For a simple webserver, sure; RH 8/9 is fine. For production database and application servers, I'd go for Advanced Server any day.
My question is, if the whole planet now sounds like Ford Prefect is somewhere in the area, where's my electric thumb and my copy of that book with the "Don't Panic" cover?
This is the best comment on the state of the current political and social climate that I have yet seen.
Brilliant.
Considering that TiVo hasn't advertised at all in three years, and seems to be living hand-to-mouth at the moment, the addition of another country might have to wait until there's a viable bottom line.
As a TiVo devotee for the past 1.5 years, though, I can only hope they make it... <crosses fingers>
I guess it depends on your inital reaction to the term hacker. It should be someone who hacks code, vs. a cracker that willfully circumvents security measures and breaks into a network. Unfortunately, you need to consider the source of the quote to get at the real meaning.
Slashdot Mirror
...our elected leaders insist on behaving like 10-year-olds, and shame on those that let them.
All this bitching is useless. Protect your investment.
Will this finally be fixed now? Sheesh.
I don't necessarily think it's astroturfing; it's a legitimate problem, and will continue to happen. OTOH, there are possible solutions, not only to this problem, but others as well. DBP, anyone?
Obvious jab at Windows and the three-a-day reboot plan aside, this is just dumb. In fact, the whole situation is just dumb. Why does it seem that Symantec/Norton <insert product here> consistently makes a bad situation much, much worse?
I might just use RHN or Red Carpet, or one of many others to patch and upgrade a few hundred Linux boxes in 10 minutes.
But that's just me.
Nope. That should never happen.
The problem here is that application-level firewalling is fraught with problems. The lack of intuitive management for this type of firewalling is a problem that quite a few companies are trying to solve -- with limited success, so far. The problem is that as you move up the OSI layers, the variables increase exponentially. If you think that 65,536 is a big number, try writing an application-level script that permits "acceptable" MAPI requests while denying "unacceptable" MAPI requests. How do you determine that this NFS packet is good, and this one is bad? From the same host to the same server? How about X11? SSH? Oh, and don't break anything while you're at it. Lions and tigers and bears, Oh my!
These are the problems of an immature technology. As time passes, these issues might be somewhat mitigated, but there are plenty of "network administrators" that haven't fully grasped the concept of IP, and struggle with L3/L4 firewalling, to say nothing of moving up the stack.
Here's a tip, though; look for Bayesian filters in firewalls in a few years. That will be a trip.
At what cost? Routers are working harder, code has been introduced into core servers that has no technical reason to exist, and an IP address, or possibly a sizeable range of IP addresses are now blacklisted worldwide. Those IPs won't be usable for anything anymore, or at least until we see widespread adoption of IPv6. *cough*
What the Internet doesn't need is to become even less of an end-to-end transport, less reliable. And we did it to ourselves.
We're on the side of the plaintiff?
It's a bad sign if you're cheering this on. Yes, VeriSign is completely wrong here, but the other party isn't to be lauded, either.
It's kinda like Carrot Top fighting Regis Philbin. Although Regis doesn't suddenly appear when I make a wrong turn.
I'm with ya.
I've been running a Promise SuperTrak 6000 for a a little more than a year now. It's been reliable, but there are NO useful diagnostics, no management, and the pti_st modules are sketchy.
That said, it's been very reliable on 2.4.20; I haven't lost a byte. *knocks wood*
We've gone plaid. Settle down, everyone, and enjoy the show. This will solidify the GPL and the viability of OSS in a federal court. Kick ass.
I bet they'd make another billion.
Please read the rest of this thread to get the general idea. Home users want things to work, period. They think in binary, even if they don't know it: "It works" or "It doesn't work".
The issue is with the lack of acceptance of patch download/installations, and the saturation of low-bandwidth links while downloading SP[1-9] at 100+MB.
Moderators, think before moderating. Posters, think before posting, please.
Automatic protection from running applications that break following a patch? At least a corporate user can call the helpdesk, while a novice home user would have no idea why something stopped working suddenly, and would chalk it up to "Computers are evil". The divide between the tech-aware and tech-unaware grows exponentially.
How hard is it to script a backup of MD5 sums to removeable media? Sheesh.
Sell SCO short.
NPR sez he's promised to.... how can he justify that with such an overwhelming nay vote in the house?
You're in luck. No A/V data flows through AOL at all.
This whole thing seems more and more like a bad movie.
It's really a matter of hardware and longer development cycles. For instance, it's hard to get HP FC HBA drivers for RH8/9, but drivers for RH AS 2.1 are available. This is true for a number of HBA vendors. The same can be said for other vendor provided drivers. They don't want to release binary-only modules for 15 revs of the kernel if they don't have to.
The other side is the longer release cycle. A server doesn't need everything and the kitchen sync, but relies upon the viability of the core applications. On AS, this code is arguably more stable, and minimizes the "extra" code. Also, anyone doing Oracle on Linux needs AS 2.1, hands down.
For a simple webserver, sure; RH 8/9 is fine. For production database and application servers, I'd go for Advanced Server any day.
This is the best comment on the state of the current political and social climate that I have yet seen. Brilliant.
Considering that TiVo hasn't advertised at all in three years, and seems to be living hand-to-mouth at the moment, the addition of another country might have to wait until there's a viable bottom line.
As a TiVo devotee for the past 1.5 years, though, I can only hope they make it... <crosses fingers>
Safecracking is an "art" too.
I guess it depends on your inital reaction to the term hacker. It should be someone who hacks code, vs. a cracker that willfully circumvents security measures and breaks into a network. Unfortunately, you need to consider the source of the quote to get at the real meaning.
And when was it ever a good time to be SBC?