Even though there might be an "exploit," writing the virus in the first place is wrong.
Never said it wasn't...
However, MS makes it really damn easy by making the same mistakes over and over and over again.
That's one of the reasons I like Linux. With so many people looking at code, the odds of something terrible getting through are greatly lowered. Yes, I said lowered; there have been bugs that have gotten through the review process. But as time goes on, they are fewer and further between.
Unlike MS... So, what's going to be the first new MS exploit of 2002?
The flight sim looks like yet another case of one branch of MS not talking to the other to find out the proper way to do things...
Re:More viri on MS- why?
on
Linux Virus Alert
·
· Score: 4, Informative
Part of it's because of the relative lack of security on a Windows box; only NT and XP had/have an administrator level where regular users aren't allowed to do things.
95/98 let anyone run just about anything as default. And XP actually does this too... Default accounts are set up as administrator without passwords.
And while you can run everything from an administrator account (got root?) under Linux, the type of person who installs Linux generally knows better than to do so.
It's because of the limited access that most accounts have that makes viruses difficult to write under Linux.
As to why malicious coders concentrate on MS, it's because it's easy. The coders at MS keep making the same mistakes over and over again. Look at the UPNP exploits.
Not as far as I know... I was a computer engineering student, and I regularly worked with the grad students, mostly as a gofer.
Mostly, they worked with pre-existing software packages; when they needed to actually write anything, it would be in C/C++ or LISP - sometimes both at once.
And let me tell you, embedded LISP code inside a C programer is really ugly looking...
My dad still makes the mistake of refering to hard drive size in megabytes, because that's what he started with...
Makes me wonder how long it will be before we have commercially available (~$200-$300) terabyte drives... And how long it will be before we have apps that require them...
I go through the meta-mods fairly quickly, looking for things that have been down-mod'd, and if it's Redundant or Over-rated, I check the context of the post (but not the author), and it usually gets mod'd back up.
The law on this is now fairly clear - since Slashdot has the power to remove comments from the database, once we receive a complaint about any particular comment we're essentially "on the hook" for its content.
Don't mod me up for this... Public service only...
final:
- Al Viro: floppy_eject cleanup, mount cleanups
- Jens Axboe: bio updates
- Ingo Molnar: mempool fixes
- GOTO Masanori: Fix O_DIRECT error handling
pre11:
- Jeff Garzik: no longer support old cards in tulip driver
(see separate driver for old tulip chips)
- Pat Mochel: driverfs/device model documentation
- Ballabio Dario: update eata driver to new IO locking
- Ingo Molnar: raid resync with new bio structures (much more efficient)
and mempool_resize()
- Jens Axboe: bio queue locking
pre10:
- Jens Axboe: more bio stuff
- Ingo Molnar: mempool for bio
- Niibe Yutaka: Super-H update
pre9:
- Jeff Garzik: separate out handling of older tulip chips
- Jens Axboe: more bio stuff
- Anton Altaparmakov: NTFS 1.1.21 update
pre8:
- Greg KH: USB updates
- Jens Axboe: more bio updates
- Christoph Rohland: fix up proper shmat semantics
pre7:
- Jens Axboe: more bio fixes/cleanups/breakage;)
- Al Viro: superblock cleanups, boot/root mounting.
pre6:
- Jens Axboe: more bio stuff
- Coda compile fixes
- Nathan Laredo: stradis driver update
pre5:
- Patrick Mochel: driver model infrastructure, part 1
- Jens Axboe: more bio fixes, cleanups
- Andrew Morton: release locking fixes
- Al Viro: superblock/mount handling
- Kai Germaschewski: AVM Fritz!Card ISDN driver
- Christoph Hellwig: make cramfs SMP-safe.
pre4:
- Jens Axboe: fix up bio highmem breakage, more cleanups
- Greg KH: USB update
pre3:
- Al Viro: more superblock cleanups
- Jens Axboe: more patches for new block IO layer
- Christoph Hellwig: get rid of the old, long- deprecated SCSI error
handling
pre2:
- Greg KH: USB update
- Richard Gooch: refcounting for devfs
- Jens Axboe: start of new block IO layer
pre1:
- me: README references to 2.4.x -> 2.5.x
- Alexander Viro: fix unmount inode breakage, show_vfsmnt cleanup
- Jeff Garzik: fix 8139too initialization
Well, when the X-Box sets a couple dozen apartments, dorm rooms, and/or houses on fire, due to the overwhelming lack of heat dissipation in the unit, that will be a big black eye for MS.
One wonders how they will word the recall annoucement so that they can spin it as not their fault....
Slashdot Mirror
...the big questions won't necessarily be how might these affect the environment as much as they will be, how with these affect the surfing...
After all, I could just run coax to all the TVs in a house. Is this somehow different because it's wireless???
I mean, whenever I buy a special package, i.e., a pay-per-view, I can watch it on all the TVs in the house...
Even though there might be an "exploit," writing the virus in the first place is wrong.
Never said it wasn't...
However, MS makes it really damn easy by making the same mistakes over and over and over again.
That's one of the reasons I like Linux. With so many people looking at code, the odds of something terrible getting through are greatly lowered. Yes, I said lowered; there have been bugs that have gotten through the review process. But as time goes on, they are fewer and further between.
Unlike MS... So, what's going to be the first new MS exploit of 2002?
Hey, I never said that they did it right...
The flight sim looks like yet another case of one branch of MS not talking to the other to find out the proper way to do things...
Part of it's because of the relative lack of security on a Windows box; only NT and XP had/have an administrator level where regular users aren't allowed to do things.
95/98 let anyone run just about anything as default. And XP actually does this too... Default accounts are set up as administrator without passwords.
And while you can run everything from an administrator account (got root?) under Linux, the type of person who installs Linux generally knows better than to do so.
It's because of the limited access that most accounts have that makes viruses difficult to write under Linux.
As to why malicious coders concentrate on MS, it's because it's easy. The coders at MS keep making the same mistakes over and over again. Look at the UPNP exploits.
Not as far as I know... I was a computer engineering student, and I regularly worked with the grad students, mostly as a gofer.
Mostly, they worked with pre-existing software packages; when they needed to actually write anything, it would be in C/C++ or LISP - sometimes both at once.
And let me tell you, embedded LISP code inside a C programer is really ugly looking...
Yeah, but you probably have the system set up in a well ventilated area.
Your average collage student, however, is going to let dust collect, and possiblly have dirty laundry or pizza boxes stacked around it.
And that will cause it to overheat, and catch some dorm on fire.
And I don't think that this will happen just once. It's going to happen multiple times.
I wonder where the retraction will be printed...
Normally those things are buried on like page 9 in really small type...
My first was a TRS-80.
Tape drive, two semi-reliable disk drives, and cartrages...
I just adjust better to the change than he does.
My dad still makes the mistake of refering to hard drive size in megabytes, because that's what he started with...
Makes me wonder how long it will be before we have commercially available (~$200-$300) terabyte drives... And how long it will be before we have apps that require them...
I'm with you on the meta-moderation...
I go through the meta-mods fairly quickly, looking for things that have been down-mod'd, and if it's Redundant or Over-rated, I check the context of the post (but not the author), and it usually gets mod'd back up.
Redundant is actually the one I'm hardest on...
The law on this is now fairly clear - since Slashdot has the power to remove comments from the database, once we receive a complaint about any particular comment we're essentially "on the hook" for its content.
Really? How does that interact with the Court ruling that message board posts are opinions, not facts?
Yet another reason not to get an Yecks-Box...
The first, of course, being Metal Gear Solid 2.
No, they didn't outwit Boise and Klein.
Those two caught MS. It was the DoJ who pulled a bait and switch on the states...
A lot of people say this was because Bush won the Presidental election. I don't know for certain...
But it was the DoJ who backed off. Check your facts.
Don't mod me up for this... Public service only...
;)
final:
- Al Viro: floppy_eject cleanup, mount cleanups
- Jens Axboe: bio updates
- Ingo Molnar: mempool fixes
- GOTO Masanori: Fix O_DIRECT error handling
pre11:
- Jeff Garzik: no longer support old cards in tulip driver
(see separate driver for old tulip chips)
- Pat Mochel: driverfs/device model documentation
- Ballabio Dario: update eata driver to new IO locking
- Ingo Molnar: raid resync with new bio structures (much more efficient)
and mempool_resize()
- Jens Axboe: bio queue locking
pre10:
- Jens Axboe: more bio stuff
- Ingo Molnar: mempool for bio
- Niibe Yutaka: Super-H update
pre9:
- Jeff Garzik: separate out handling of older tulip chips
- Jens Axboe: more bio stuff
- Anton Altaparmakov: NTFS 1.1.21 update
pre8:
- Greg KH: USB updates
- Jens Axboe: more bio updates
- Christoph Rohland: fix up proper shmat semantics
pre7:
- Jens Axboe: more bio fixes/cleanups/breakage
- Al Viro: superblock cleanups, boot/root mounting.
pre6:
- Jens Axboe: more bio stuff
- Coda compile fixes
- Nathan Laredo: stradis driver update
pre5:
- Patrick Mochel: driver model infrastructure, part 1
- Jens Axboe: more bio fixes, cleanups
- Andrew Morton: release locking fixes
- Al Viro: superblock/mount handling
- Kai Germaschewski: AVM Fritz!Card ISDN driver
- Christoph Hellwig: make cramfs SMP-safe.
pre4:
- Jens Axboe: fix up bio highmem breakage, more cleanups
- Greg KH: USB update
pre3:
- Al Viro: more superblock cleanups
- Jens Axboe: more patches for new block IO layer
- Christoph Hellwig: get rid of the old, long- deprecated SCSI error
handling
pre2:
- Greg KH: USB update
- Richard Gooch: refcounting for devfs
- Jens Axboe: start of new block IO layer
pre1:
- me: README references to 2.4.x -> 2.5.x
- Alexander Viro: fix unmount inode breakage, show_vfsmnt cleanup
- Jeff Garzik: fix 8139too initialization
And will this cause the /. effect on Microsoft?
That would be neat...
Why would you need to embed video files into a Word document to begin with???
Well, when the X-Box sets a couple dozen apartments, dorm rooms, and/or houses on fire, due to the overwhelming lack of heat dissipation in the unit, that will be a big black eye for MS.
One wonders how they will word the recall annoucement so that they can spin it as not their fault....
How many of the features of Word or Excel does the average person use?
I use WordPerfect to do word processing. It does everything I need, with half the bloat of Word.
Likewise, when I do need a spreadsheet (rarely), I use Quattro, as it does everything I need, with again, half the bloat.
All the bells and whistles of MS products don't mean a thing to me, other than extra hard drive space... Which I can't afford.
Isn't he part owner of the company he works for?
So he'd be going free in exchange for testemony against himself???
Of course not...
Everyone knows that Java and Microsoft don't blend....
If so, it would probably be more expensive than it's worth... I.e, buying a new car to take advantage of this would be cheaper...
Personally, I don't think that Linus would have allowed something like this to get through in the first place.
But that's just me.
Right, but NSA Linux isn't necessarily like the others....
The national versions of Linux may be considered similar to the national airlines, i.e., the flag carriers.
Personally, if I had a available computer to put it on, I'd give the NSA Linux a try.
The reason it takes so long to transfer money is because that's what PayPal's primary income source is - interest on your money.
Look at it like this:
You pay money to a merchant, he lets it sit there for a couple of weeks before he pulls it out.
The merchant pays a small amount to PayPal for the convienence, but the big money comes from the interest on the money.
$50 for two weeks might not seem like much, but multiply it by thousands, and it adds up quick.
Consequently, when you want to take money out, they have the transaction take a couple of extra days to squeeze every drop of interest.