This is like pushing s.up.h & as much as it pains me to leap to the defence,lol, of closed source who out there is writing "spyware/virus/trojans/worms" for the other minor percent of desktop o.s's when you can attack the o.s. at the top of the heap.Originally posted by Goslow unplugged+Dec 18 2003, 05:07 AM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (Goslow unplugged @ Dec 18 2003, 05:07 AM)</td></tr><tr><td id='QUOTE'><!--QuoteBegin--locustfurnace@Dec 18 2003, 02:44 AM
I guess thats just a bonus & reward to the Windows user-base, or possibly "buried treasure" inside each win-tel box!
----------------------------
BIG
BLUE If you don't like those kinds of thrills wait until the software is "out of" beta.[/b][/quote]
well it does not work the same, even IF people write virii for other OS's, not just the open source, there is still PLENTY of closed Source OS's on the market. For most part, the virii run rampant on Windows do to its lackluster security.
On the other OS's, (which really are dominant in the server market), the programs can not run on their own with out permissions. This is why they - the OS's, are used in the server market more then Windows, I dont recall Windows scaling up to the BIG IRON either. Thats usually left to UNICES, like AIX, HP.
Without user ID's and Group IDs, viruses that DO make it on those boxes, can not run. Even if you do replace some daemons with trojans, alot of Admins will run - or should run their daemons chroot or jail em.
If a user purposesly downloads a virus on a Server OS, and executes it, it would only ruin their own home dir, as they, Virus, would not have access beyond /usr/home/*
also, binarys MUST be placed in the PATH, such as /bin / usr/bin / /usr/sbin, and to be able to add a binary to these directorys, someone with root permissions & password is the only one who can add these binarys to those directorys. It is very uncommon to be able to run binaries from userland. they have to run in the directorys that are laid out for them. So Joe User, can not place a virus in these path directorys to make them run. if he does not have root or su/wheel permission & password.
plus you have kernel securelevels and can chflags binarys and directorys which can accomplish many things such as deny the chflaged binary from being deleted, overwritten, or amened.
Windows will run a binary anywhere you place it. It has no set area that has flags for "CAN RUN" & "CAN'T RUN"
File also have different attributes in other OS's, such as the attribute to be executable. Windows will run anything that ends in an .exe. While under Unix the file must have the attribute to be able to run, even if it is a binary file, if the permissions are not set for it to be able to run, then it wont run.
Mac OS does not suffer from viruese either, neither does Os/2, Ecomm Station, BeOS, QNX, .........